Messaging Send API
Reference page for submitting notification delivery requests to registered application devices.
POST /v1/messaging/send
Status
OperationalThe endpoint accepts authenticated delivery requests and queues messages for regional fanout. Requests are validated before enqueueing.
Current Limits
Normal| Max payload | 4096 bytes |
| Batch size | 500 tokens |
| Retry window | 15 minutes |
| Timeout | 30 seconds |
Request Fields
| Field | Type | Required | Description |
|---|---|---|---|
token | string | Yes | Device registration token or delivery target alias. |
notification.title | string | No | Displayed title for user-visible notifications. |
notification.body | string | No | Displayed body content for user-visible notifications. |
data | object | No | Custom key-value payload for application handlers. |
priority | string | No | Delivery priority. Accepted values are normal and high. |
Example Request
{
"token": "device-token",
"notification": {
"title": "Account update",
"body": "Your project settings were updated."
},
"data": {
"project": "default",
"event": "settings.updated"
},
"priority": "normal"
}
Response Codes
| Code | Meaning | Action |
|---|---|---|
200 | Queued | The request was accepted for delivery. |
400 | Invalid request | Check payload shape and field limits. |
401 | Unauthorized | Refresh credentials and retry. |
429 | Rate limited | Retry with exponential backoff. |
503 | Temporarily unavailable | Retry after the indicated interval. |