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 legacyX-Idempotenciais still accepted for old producers but new code should not send it. - Deliveries carry
X-Event-Hub-Event,X-Event-Hub-AttemptandX-Event-Hub-Signature(sha256=<hex>).
MIT licensed.
Metadata
Release files for full-event-hub 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| full_event_hub-1.2.0.tar.gz | 8.5 kB | With provenance | Details for full_event_hub-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| full_event_hub-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for full_event_hub-1.2.0-py3-none-any.whl |
Total release size: 15.9 kB
Release files / full_event_hub-1.2.0.tar.gz
| Download URL | full_event_hub-1.2.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7373f93d38d7c35c8b13af7f794ce7c1b05b5cfd980e21e05082fb994dcb42f8
|
|
BLAKE2b-256 checksum How to use checksums |
e4c88725e52dba823d987371ac82d6f05eead170bb2009da3f339647d8378bdf
|
| 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 Oct 25, 2026.
Transparency logRelease files / full_event_hub-1.2.0-py3-none-any.whl
| Download URL | full_event_hub-1.2.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
50b5b20166bcfae88678dbc2b597013c3af4c7cec2db171c31777604743c19b2
|
|
BLAKE2b-256 checksum How to use checksums |
06fb76971c4a527c98e48dcb315f73730081bbb2c4e06292caa0d78880ec69db
|
| 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 Oct 25, 2026.
Transparency logSecurity for full-event-hub 1.2.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.
Attestation for full_event_hub-1.2.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 Oct 25, 2026.
Transparency logA 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.