Experience API v1
Webhooks console
Manage your bundled-request webhook subscriptions and inspect their delivery history —
the same /DisbursementRequests/WebhookSubscriptions endpoints your integration
calls, without leaving the portal.
GET /Integration
is authoritative: when it reports features.webhooks: false, the subscription
endpoints return 404 and this console shows a not-yet-enabled notice for your
token. Webhooks are emitted only for bundled requests created with
POST /DisbursementRequests, not for granular /Disbursement resources.
Webhooks are notifications; the Events feed (GET /DisbursementRequests/Events)
is the authoritative record, so your integration must work without them.
Connect with your API token
Paste an Experience API access token from your OAuth client-credentials flow — the same
token you send from curl or Postman (see
step 1 of the quickstart). The token
stays in this browser tab's memory only: the portal forwards it with each console request
to the Experience API and never stores or logs it. This console calls https://api.direcfunds.com; use a short-lived token issued for that environment.
Webhooks are not yet enabled for your integration
Your token authenticated, but GET /Integration reports
features.webhooks: false, so the subscription endpoints answer
404 for this integration. Webhook delivery is switched on per
integration during rollout.
Track request state with GET /DisbursementRequests/Events in the meantime.
To ask about webhook enablement, email
support@direcfunds.com. The
API integration guide covers the envelope,
signature scheme, and retry policy end to end.
Subscriptions
| Callback URL | Event coverage | Status | Created (UTC) | Signature | Actions |
|---|
No subscriptions yet. Create one below — start with event coverage * for the
webhook-first integration.
New subscription
Store this signing secret now
Store it in your secret manager before leaving or reloading this page. The list and
update calls never return a secret, and there is no read-by-id call. Only an exact
replay of the API create request (same X-Idempotency-Key and body) within
48 hours returns a DirecFunds-generated secret again; a secret you supplied yourself is
never echoed back. This console creates a fresh key for each submission, so save the
displayed secret before leaving.
Delivery log
| Delivery | Event id | Event type | Status | Attempts | Last error | Created (UTC) | Delivered / next attempt (UTC) | Actions |
|---|
No deliveries match this filter yet.
Deliveries are at-least-once with ten attempts in total. Receivers have 15 seconds;
redirects are not followed and only 2xx acknowledges delivery. Without a
Retry-After header, retries back off exponentially: the longest delay is about
43 minutes and the whole automatic budget is about 85 minutes. A Retry-After on a
non-2xx response replaces the backoff for that attempt, with no minimum and capped at one
hour, so a short Retry-After can use up all ten attempts within minutes. Timeouts
and connection failures always use the backoff.
A DeadLettered delivery has exhausted every automatic attempt — redeliver
it once your receiver is healthy again and the subscription is active. Disabled subscriptions dead-letter deliveries and refuse redelivery. The repeat carries the same
X-DirecFunds-Event-Id (the Event id column), so receivers that already
committed it must treat it as a duplicate and return 2xx.
To catch up after an outage, replay GET /DisbursementRequests/Events from the
last feed id you processed, using that feed's own id and
nextCursor as the after value. Do not use a webhook's
sequence as the feed cursor; it is not the same counter.
Build your receiver
- Webhook subscriptions and event catalog — envelope fields, delivery headers, signature scheme, and retry policy.
- C# webhook signature verification — constant-time HMAC-SHA256 check to run before parsing any delivery.
- Webhook secret rotation — rotate a signing secret in place without duplicating events.