Send a push notification

One call: to + title + body. to is exactly one of { phone }, { email }, { contactId }, { deviceId } or { testDevices: true }; every device the person has registered receives it. Optional: image (https), url (deep link opened on tap), up to 3 buttons, countdownEndAt (a live countdown on Android, "Ends 8:00 pm" on iOS), data your app reads, kind (promotional needs the device's marketing opt-in and respects quiet hours and the daily cap — default transactional), sendAt, collapseKey, ttlSeconds, dryRun.

Answers 202 at once: status is queued / scheduled, or no_recipients when the person has no eligible device (a state, not an error — recipients.excluded says why). Sending happens within a few seconds; follow it with Get push message (a push is not a chat message and raises no message.* webhook). Lists and segments are campaigns: create one on the push channel with the Campaigns API.

Authenticate with your organisation API token (Bearer). Roles: CRM_ADMIN, ACCOUNT_OWNER or CRM_BOT.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Your organisation id (the one your API token was issued for).

Body Params
Headers
string

A unique string of 1–255 printable ASCII characters without spaces, e.g. a UUID per push you intend to send. Repeating a request with the same key returns the answer the first one got (200, Idempotent-Replayed: true, replayed: true) instead of sending again; the same key with a different body is a 422; a repeat while the first request is still running is a 409 (retry in a few seconds). A request that sent nothing (a dry run, no_recipients, a 400 / 404, a 503 that says nothing was sent) leaves the key unused. Keys are remembered as long as the push is (31 days after it is sent). Strongly recommended — retries after a timeout then never double-send.

Responses
200

Replayed — the answer this Idempotency-Key already got (replayed: true)

400

Invalid message or recipient (error.code says what), or a malformed Idempotency-Key

401

Token missing, invalid or for another organisation

403

The token holder lacks the required role

404

Contact, device or push channel not found

409

A request with this Idempotency-Key is still being processed — retry in a few seconds

422

Idempotency-Key reused with a different body

429

Rate limited — retry after the Retry-After header

503

Push notifications are not available on this server yet

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