# Bulk Resending Callbacks
This API allows you to send callbacks for a list of transactions. Callbacks are sent asynchronously. The basic principles of working with the API are described above (opens new window).
Requires the secure_heartbeat_notifications.write scope, which must be requested during authentication.
| Parameter | Type | Required | Description |
|---|---|---|---|
| ids | array | Yes | id payments (opens new window) |
Request:
curl --location 'https://secure.mandarinpay.com/api/notifications/bulk' \
--header 'Mid: 6019' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer Nwii9xFAfHjAWkk6PPOFUmpheFe123' \
--data '{
"ids": ["43913ddc000c4d3990fddbd3980c1725", "1e68b13b34e247fd9ac3583ae9947127"]
}'
Response if the request is successfully created (state: Scheduled):
{
"notifications": [{
"transactionId": "43913ddc000c4d3990fddbd3980c1725",
"state": "Scheduled"
},
{
"transactionId": "1e68b13b34e247fd9ac3583ae9947127",
"state": "Scheduled"
}
],
"total": 2,
"scheduled": 2,
"skipped": 0
}
Response if the send request was ignored (state: Skipped):
{
"notifications": [{
"transactionId": "43913ddc000c4d3990fddbd3980c1725",
"state": "Skipped"
},
{
"transactionId": "1e68b13b34e247fd9ac3583ae9947127",
"state": "Skipped"
}
],
"total": 2,
"scheduled": 0,
"skipped": 2
}
Main reasons for the Skipped status:
- The client whose Bearer token was passed in the headers does not have access to the operation - the request is sent for operations belonging to a different Client ID. We recommend checking the correctness of the operation IDs or authorization.
- Operation not found - an operation with this ID was not found in the system.