Resend Webhook

This API creates a webhook resend request for cash-in (QR Code) or cash-out (Transaction) events. You can resend specific webhooks by object ID or perform a bulk resend for all webhooks within a specified time period for an account.

Headers

ParameterTypeDescriptionExample
AuthorizationStringBearer + Access_tokenBearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ0b2tlbl90eXBlIjoiYWNjZXNzIiwiZXhwIjoxNzEzMzAwOTMxLCJpYXQiOjE3MTMyOTczMzEsImp0aSI6Ijc2ZWI4ZTE5ZjM4YjQ4NmZiODdmNzNjNTdkMWVmNDJhIiwidXNlcl9pZCI6MjQ2fQ.5zekMa7CUj9p-MvNHns5ke4ZPhYV3Y1CLOsYL7hDUUo

Body Details

{
  "resend_type": "CASHIN",
  "object_reference_id": 12345,
  "source_account_branch_identifier": "0001",
  "source_account_number": "123456",
  "start_datetime": "2026-05-01T00:00:00Z",
  "end_datetime": "2026-05-12T23:59:59Z"
}
FieldTypeDescriptionRequired or Optional
resend_typeStringType of webhook to resend. Valid values: CASHIN (for QR Code) or CASHOUT (for Transaction).required
object_reference_idIntegerID of the specific object to resend webhook for. For CASHIN: QR Code ID. For CASHOUT: Transaction ID.optional
source_account_branch_identifierStringBranch identifier of the source account. Required when using date range filters (start_datetime/end_datetime).optional
source_account_numberStringAccount number of the source account. Required when using date range filters (start_datetime/end_datetime).optional
start_datetimeDateTimeStart date and time for bulk resend (ISO 8601 format). Requires account identification.optional
end_datetimeDateTimeEnd date and time for bulk resend (ISO 8601 format). Requires account identification.optional

Request Examples

Resend webhook for a specific QR Code (CASHIN):

POST /v3/webhooks/resend
Authorization: Bearer <access_token>
Content-Type: application/json

{
  "resend_type": "CASHIN",
  "object_reference_id": 12345
}

Resend webhook for a specific Transaction (CASHOUT):

POST /v3/webhooks/resend
Authorization: Bearer <access_token>
Content-Type: application/json

{
  "resend_type": "CASHOUT",
  "object_reference_id": 98765
}

Bulk resend webhooks for a source account in a date range:

POST /v3/webhooks/resend
Authorization: Bearer <access_token>
Content-Type: application/json

{
  "resend_type": "CASHIN",
  "source_account_branch_identifier": "0001",
  "source_account_number": "123456",
  "start_datetime": "2026-05-01T00:00:00Z",
  "end_datetime": "2026-05-12T23:59:59Z"
}

Response Details

{
  "worked": true,
  "detail": "Webhook resend request created. ID: 7890"
}
FieldTypeDescription
workedBooleantrue when the resend request was successfully created, false on error.
detailStringSuccess message with the resend log ID, or error description when failed.

Error Responses

HTTP CodeError MessageDescription
400QR Code not foundThe specified QR Code ID does not exist or you do not have access to it.
400Transaction not foundThe specified Transaction ID does not exist or you do not have access to it.
400Account not foundThe account identified by branch and account number was not found or is not accessible.
401UnauthorizedInvalid or missing authentication token. Ensure you are sending a valid Bearer token.
422Validation errorRequest validation failed. Check that all required fields are present and in the correct format.

Business Rules

Authentication:

  • Requires valid authentication token
  • User must be authenticated

Resend Modes:

  • Resend webhook for a specific object by providing object_reference_id
  • Perform bulk resend by providing date range (start_datetime and end_datetime) along with account identification
  • When using date range filters, both source_account_branch_identifier and source_account_number are required

Validations:

  • For CASHIN type: Must provide either object_reference_id or all date range parameters
  • For CASHOUT type: Must provide either object_reference_id or all date range parameters
  • You can only resend webhooks for objects and accounts that you have access to
  • Date range requires all four fields: branch identifier, account number, start datetime, and end datetime

Processing:

  • The resend request is processed asynchronously in the background
  • The response returns immediately with a request ID
  • Use the List Webhook Resend Logs endpoint to check the processing status
Responses

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json