/api/v1/webhooks/resend Request authentication
Include X-Bolt-Key, X-Bolt-Timestamp and X-Bolt-Signature. Use a current millisecond timestamp and sign it together with the exact request body.
When to resend
Use this endpoint when your system needs another notification of a confirmed payment. Resending does not collect payment, reconcile a transfer or create an order.
Only your own CONFIRMED or COMPLETED orders can be resent. PENDING, PAID and other states are not eligible.
An available, active Webhook configuration is required. If no delivery task is persisted, the endpoint returns an error instead of QUEUED.
01. Request parameters
application/jsonSend the merchant externalOrderId supplied at order creation, not orderToken. You can only resend notifications for orders belonging to the current API key.
Example value
{"externalOrderId": "INV-20260209-99281"}Required string, 6–64 characters. Letters, digits, underscores (_) and hyphens (-) are allowed.
02. Response fields (data)
application/jsonQUEUED means a delivery task was persisted for asynchronous sending, not that it was delivered. Check delivery logs in the merchant dashboard for the recipient’s HTTP 2xx response.
Recipient handling
Verify X-Bolt-Webhook-Timestamp and X-Bolt-Webhook-Signature, then deduplicate by eventId or merchant order ID before fulfillment. Return HTTP 2xx for duplicate notifications that were already handled successfully.
- triggerType: MANUAL appears in the resend response and dashboard delivery records. The current Webhook request body does not contain triggerType; do not depend on it to identify a resend.
- Each successful call creates an independent delivery task. Repeated requests may send multiple notifications. Check delivery logs before resending again. Replays retain the logical eventId.
- This endpoint reuses the order’s callback destination and does not accept a new URL. Changing the dashboard default does not replace an address already saved on the order.
Common errors
These are common cases. Use the actual HTTP status and response code/message to diagnose failures. An error response is not a payment result.
- 401: Check the API Key, raw-body signature and current millisecond timestamp (within 5 minutes of the server clock).
- 404: The order is missing, belongs to another merchant or is outside the history allowed by your plan.
- 400: The order is not CONFIRMED / COMPLETED, or an available Webhook configuration and a successfully stored delivery task are missing.