Send one message to multiple recipients (async)
Queues one notification per recipient. Always asynchronous: the 202 means jobs were queued, not that anything was delivered.
COMPARE total_requested WITH queued_count ON EVERY CALL. They differ when a recipient is inactive — that recipient is skipped and nothing else in the response says so. queued_recipient_uuids lists exactly who was queued, in UUIDs you can match against what you sent; the difference between that list and your input is who was silently skipped.
A request in which NOT ONE recipient could be queued is refused with 422 and code: BULK_NOTHING_QUEUED rather than answered 202 with a zero count, because "successfully queued nobody" reads as success.
Unknown, deleted or other-company UUIDs are a 422 on the request as a whole — nothing is queued, so a typo cannot half-send a batch. Follow each queued notification through GET /api/v1/notifications/{notification}/status; this endpoint returns no notification UUIDs, so find them via GET /api/v1/notifications filtered by recipient.
Request
- Base URL: https://wardenpoint.com (the document declares no server; this is the origin it was published from)
- URL: https://wardenpoint.com/api/v1/notifications/send-bulk-async
- Auth: API key in header X-API-Key
Request body
Example request
{
"channel_type": "text_message",
"provider": "telegram"
}Response
At least one notification was queued.
Example response
{
"success": true,
"queued": true
}Changes
No recorded changes to this operation across all 1 revision of this API.