Webhook Access & Delivery

Access is permission- and rollout-controlled. Credential V2 webhook management requires an active organization-bound x-api-key with audience webhooks and scope webhooks.manage; its quota is 60 requests/minute per credential/organization/scope. Key format alone does not enable event delivery.

Availability model

/api/v1/webhooks accepts only analysis/passport events and stores subscriptions in a process-local Map. It is a limited control-plane surface, not a durable Marketplace quote/order subscription API. Commercial tier labels do not prove a purchasable membership package or automatic event access.

Durable Marketplace delivery uses a separate organization-scoped Firestore subscription/delivery adapter and dispatch cron. Confirm the approved subscription, mapped producer events, dispatcher operation and rollout before relying on it. Public Master Data data-product delivery remains external-dark.

Delivery expectations

The durable path uses signed HTTPS requests, bounded retries, lease-fenced updates and terminal failure state. Consumers must deduplicate and reconcile missed/failed work. The process-local management helper has a different failure counter and does not inherit these durable guarantees.

Security basics

Verify the exact route's signature contract before parsing. Durable Marketplace supports Standard Webhooks and a timestamped legacy signature; the management helper uses a raw-body signature; inbound XJMF uses sender-registry HMAC plus a separate timestamp check. Return 2xx after verified durable acceptance and process heavy work asynchronously. See the webhook guide for header formats and boundaries.

Related Articles