Signed webhooks
Send stable event IDs, timestamps, raw-body signatures, fixed retry payloads, and replayable delivery history.
Build webhooks →Feed syndication
Feed syndication and webhook subscriptions.
Route normalized developer updates into signed webhooks, team digests, APIs, archives, and custom feeds without coupling delivery to source polling.
TriggerPoll, WebSub, provider webhook
MatchTenant and topic filters
DeliverSigned, idempotent events
RecoverRetry, dead letter, replay
Destinations
Generate several views from one canonical history.
Destination-specific formatting belongs after normalization, so the same source record can serve machines and people without disagreement.
Custom RSS feeds
Compose tenant, product, environment, or topic views with stable item identity and canonical links.
Design custom feeds →JSON API streams
Expose snapshots and cursor-ordered changes for applications that prefer pull-based synchronization.
Review API design →Team digests
Group related releases or articles into readable summaries without changing the underlying event records.
Curate release signals →Archive exports
Retain normalized history with explicit paging, timestamps, provenance, and policy-based retention.
Plan archives →Operational events
Feed internal queues and observability systems with source, entry, subscription, and delivery identifiers.
Measure the pipeline →Delivery contract
Accept once. Deliver idempotently. Replay deliberately.
A source update should be durable before any destination is called.
1
Commit change eventsRecord created, updated, or withdrawn state with the configuration version that matched.
2
Create destination jobsGenerate a stable event and idempotency key for each subscription and destination.
3
Sign and attemptUse per-destination secrets, bounded timeouts, and safe response capture.
4
Retry or replayKeep automatic backoff separate from an operator- or customer-requested replay.
feed.entry.created
{ "event_id": "evt_01J...", "type": "feed.entry.created", "created_at": "2026-10-23T18:42:13Z", "subscription_id": "sub_01J...", "data": { "source_id": "src_01J...", "entry_id": "itm_01J..." } }
Push plus reconciliation
Use WebSub for speed and polling for completeness.
A lease-based push signal lowers delay. Scheduled reconciliation recovers missed notifications and confirms the canonical feed state.
Discover and verify
Store hub and topic separately, bind challenges to pending subscriptions, and activate only after verification.
Implement WebSub →Authenticate and deduplicate
Verify signatures over raw bodies, reject replay abuse, and deduplicate both notification events and feed entries.
Secure callbacks →Renew and reconcile
Renew leases early with jitter, keep periodic polling, and expose last push and last reconciliation.
Observe subscriptions →Keep delivery independent from ingestion.
One failing destination should never delay source discovery or corrupt canonical entry history.