Skip to main content

full-event-hub (Python client)

Zero-dependency Python client for event-hub — a webhook fan-out service (ingest, fan-out to N subscribers, HMAC signing, retry/backoff, attempts, retention).

Only the standard library is used (urllib.request, json, hmac, hashlib). The package version matches the hub/image version (ghcr.io/ravileal/event-hub); because they move together, the client sends the English X-Idempotency header that hubs since 1.1.0 read, while a hub older than 1.1.0 ignores it.

Install

pip install full-event-hub

Publish an event

from event_hub import EventHubClient

hub = EventHubClient("http://127.0.0.1:18295")

hub.create_topic("orders", description="order lifecycle")
hub.create_subscriber("orders", "billing",
                      url="http://localhost:9000/hook", secret="s3cr3t",
                      max_attempts=3, backoff_ms=200)

resp = hub.publish_event("orders", {"order_id": 1}, idempotency_key="order-1")
print(resp.status, resp.body)  # 202 {'id': 1, 'deliveries_created': 1, 'duplicado': False}

publish_event sends the idempotency key as X-Idempotency (the header the hub reads since 1.1.0; it falls back to the legacy X-Idempotencia). Use sign(secret, raw_body) to sign the exact bytes you send.

Verify an incoming delivery

event-hub signs every delivery with HMAC-SHA256 of the raw body using the subscriber secret. Pass the exact bytes received; re-serializing JSON breaks the HMAC.

from event_hub import verify_delivery_signature

# in your webhook receiver:
valid = verify_delivery_signature(
    secret, raw_body, request.headers["X-Event-Hub-Signature"]
)

verify_delivery_signature returns False for a missing header, a wrong sha256= prefix, or a non-matching digest, and compares in constant time (hmac.compare_digest).

Notes

  • Idempotency header is X-Idempotency (English) since 1.1.0; the legacy X-Idempotencia is still accepted for old producers but new code should not send it.
  • Deliveries carry X-Event-Hub-Event, X-Event-Hub-Attempt and X-Event-Hub-Signature (sha256=<hex>).

MIT licensed.

Metadata

Release files for full-event-hub 1.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for full-event-hub 1.5.0
File Size Uploaded Provenance Actions
full_event_hub-1.5.0.tar.gz 8.4 kB With provenance Details for full_event_hub-1.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for full-event-hub 1.5.0
File Interpreter ABI Platform Actions
full_event_hub-1.5.0-py3-none-any.whl Python 3 none any Details for full_event_hub-1.5.0-py3-none-any.whl

Total release size: 15.9 kB

Release files / full_event_hub-1.5.0.tar.gz

Download URL full_event_hub-1.5.0.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
860f8610786349181a758b3141e15539fb872a959aaadcc8d8e223b9c25aa14b
BLAKE2b-256 checksum
How to use checksums
7eb8c76b5152ed754a241c4d20170c902e9990169d2e48cdae600f46e14f4f11
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Release files / full_event_hub-1.5.0-py3-none-any.whl

Download URL full_event_hub-1.5.0-py3-none-any.whl
Size 7.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
654bc391a9cd931e8d77b04321b113d2629ba15f51cca926eeaef03eae64d0d0
BLAKE2b-256 checksum
How to use checksums
fe1aca718844dbfe16fc3dbffd2e2fc9d1d393f5befd78e8fdd45937514e4817
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Security for full-event-hub 1.5.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for full_event_hub-1.5.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page