Skip to content

Replay webhook delivery

POST/webhook-deliveries/{id}/replay

Resend the same event (same webhook-id). Never creates a financial event.

Sandbox: test money only. No request moves real money.

Authenticate with your sandbox key as a bearer token: Authorization: Bearer nbk_test_....

Re-arms the same delivery: the same event and webhook-id, a new timestamp and signature, its attempts numbered on and its retry schedule started again. It never creates an event, an order or a balance movement. A delivery whose endpoint is disabled is 400 invalid_request (nothing would be sent: enable the endpoint first), as a test event to it is; one of an event created more than 30 days ago is 400 invalid_request, and an endpoint's deliveries are replayed at most 10 times in any hour and one delivery at most 3 times in any day (429 rate_limited with Retry-After). A delivery being attempted right now is left to finish. Each replay is audited.

Request

HeaderValueSent
AuthorizationBearer nbk_test_...Required
Idempotency-Key3f1c9a52-7d4e-4b8a-9c21-5e6f7a8b9c0dOptional

Parameters

FieldDescription
IDid · path string · requiredPattern ^whd_[0-9A-HJKMNP-TV-Z]{26}$.
Idempotency keyIdempotency-Key · header stringBound permanently, in the database, to what the first request made (a quote, an endpoint, a rotation, a delivery replay), as a money operation's key is: a retry with the same key and request answers 200 with Idempotent-Replayed: true and repeats nothing, and the same key with another request or on another operation is 422 idempotency_key_reused. A replay never returns a secret. Without a key, every request is performed. Pattern ^[A-Za-z0-9_-]{16,64}$.
The request in cURL, JavaScript and Python
POST /v1/webhook-deliveries/{id}/replaySandbox, test key
const response = await fetch('https://sandbox-api.nasfampay.com/v1/webhook-deliveries/whd_01K7SAMP000000000000000001/replay', {  method: 'POST',  headers: {    Authorization: `Bearer ${process.env.NASFAM_SANDBOX_KEY}`,  },});if (!response.ok) {  const problem = await response.json();  throw new Error(`${problem.status} ${problem.code}: ${problem.title} (request ${problem.request_id})`);}const result = await response.json();console.log(response.status, result);
Code for Request
POST /v1/webhook-deliveries/{id}/replaySandbox, test key
// npm install axiosimport axios from 'axios';try {  const { status, data: delivery } = await axios.post(    'https://sandbox-api.nasfampay.com/v1/webhook-deliveries/whd_01K7SAMP000000000000000090/replay',    null,    {      headers: {        Authorization: `Bearer ${process.env.NASFAM_SANDBOX_KEY}`,      },    },  );  console.log(status, delivery);} catch (error) {  if (!axios.isAxiosError(error) || !error.response) throw error;  const problem = error.response.data;  throw new Error(`${problem.status} ${problem.code}: ${problem.title} (request ${problem.request_id})`);}

Responses

StatusMeaningBody
OK200A replay of an earlier request with the same Idempotency-Key: the delivery, as it is now. Nothing is re-armed again. Headers: RateLimit (draft-ietf-httpapi-ratelimit-headers-11. the same buckets, each "<bucket>";r=<whole requests remaining, never negative>;t=<seconds until the quota is fully available again>. ), RateLimit-Policy (draft-ietf-httpapi-ratelimit-headers-11. a structured field list with one item per bucket the request drew on (orders, quotes, quotes_daily, reads, webhooks, lookups, lookups_org, lookups_daily), each "<bucket>";q=<quota>;w=<window seconds>. no partition key (pk) is sent. ), Idempotent-Replayed.WebhookDelivery object
Accepted202Replay scheduled. Headers: RateLimit (draft-ietf-httpapi-ratelimit-headers-11. the same buckets, each "<bucket>";r=<whole requests remaining, never negative>;t=<seconds until the quota is fully available again>. ), RateLimit-Policy (draft-ietf-httpapi-ratelimit-headers-11. a structured field list with one item per bucket the request drew on (orders, quotes, quotes_daily, reads, webhooks, lookups, lookups_org, lookups_daily), each "<bucket>";q=<quota>;w=<window seconds>. no partition key (pk) is sent. ).WebhookDelivery object
Too many requests429Too many requests (rate_limited), or your queued orders are at your cap (queue_limit). A bucket that cannot be read at once because of contention is answered here too, never waited on. Honour Retry-After. . Headers: Request-Id, Retry-After (seconds to wait before retrying), RateLimit (draft-ietf-httpapi-ratelimit-headers-11. the same buckets, each "<bucket>";r=<whole requests remaining, never negative>;t=<seconds until the quota is fully available again>. ), RateLimit-Policy (draft-ietf-httpapi-ratelimit-headers-11. a structured field list with one item per bucket the request drew on (orders, quotes, quotes_daily, reads, webhooks, lookups, lookups_org, lookups_daily), each "<bucket>";q=<quota>;w=<window seconds>. no partition key (pk) is sent. ).Problem object
Any other statusdefaultError (RFC 9457). A 503 service_unavailable with Retry-After means the request was not processed: the rate limiter or the database could not answer, and the API refuses rather than serve unlimited (reads included). For a money-moving operation, retrying with the same Idempotency-Key is always safe. . Headers: Request-Id, Retry-After (on 429 and some 503 responses).Problem object

The webhook delivery object

FieldDescription
IDid · string · requiredPattern ^whd_[0-9A-HJKMNP-TV-Z]{26}$.
Event IDevent_id · string · required
Attemptattempt · integer · requiredAt least 1.
Statusstatus · string · requiredOne of pending, succeeded, failed, abandoned.
Response statusresponse_status · integer or null
Duration msduration_ms · integer or null
Failure classfailure_class · stringNull when accepted (2xx) or not yet attempted, and for a stored answer with no class (a 101 recorded before such answers were recorded as connection failures).
Next attempt atnext_attempt_at · string or nullFormat date-time.
Created atcreated_at · string · requiredFormat date-time.

Responses are extensible: ignore fields, enum values and event types you do not know. Any other status is a Problem (see Errors).

Every kind of response
202 AcceptedSynthetic sandbox data
{  "id": "whd_01K7SAMP000000000000000001",  "event_id": "string",  "attempt": 1,  "status": "pending",  "response_status": null,  "duration_ms": null,  "failure_class": null,  "next_attempt_at": null,  "created_at": "2026-10-10T10:05:02Z"}

Not finished. Only a final status means it is done: read it again or wait for its webhook. An outcome that is not known yet is held, never a failure.

Code for Responses
Response
JSON
202 AcceptedSynthetic sandbox data
{  "id": "whd_01K7SAMP000000000000000091",  "event_id": "evt_01K7SAMP000000000000000090",  "attempt": 1,  "status": "pending",  "created_at": "2026-10-10T10:30:00.000Z"}
Error
JSON
429 Too Many RequestsSynthetic sandbox data
{  "type": "about:blank",  "title": "Too many requests",  "status": 429,  "code": "rate_limited",  "category": "rate_limit",  "detail": "Too many requests. Retry after the time in Retry-After.",  "param": null,  "request_id": "req_01K7SAMP000000000000000090"}

How it behaves

What to expect
AuthenticationYour key as a bearer token in the Authorization header: a nbk_test_ key on the sandbox host.
IdempotencyOptional. Sent, it is bound permanently to what the first request made, and a retry repeats nothing.
In the sandboxServed, on your own test records.
On LiveThe same request, on the Live host with a live key, which exists only for a workspace activated for Live. See Go live.
FundingNone. This request does not touch your balance.
Status changesSchedules the delivery again. It never creates a financial event.
Webhook eventsThe same event, with the same webhook-id.

Error responses

This operation can also answer with not_found, idempotency_key_reused.

Any request can answer with invalid_request, invalid_api_key, key_expired, key_environment_mismatch, insufficient_scope, rate_limited, service_unavailable, internal_error. Errors says what to do about each one.