Use the /createMessage endpoint to send unique messages to different users without using tags. Include multiple objects in the notifications array, where each object has its own content and its own target user IDs.
Example payload
{
"request": {
"application": "XXXXX-XXXXX",
"auth": "YOUR_API_TOKEN",
"notifications": [
{
"send_date": "now",
"content": "Your event occurred at 22-Apr-2026 09:15:04 AM",
"users": ["user_1"]
},
{
"send_date": "now",
"content": "Your event occurred at 22-Apr-2026 09:15:30 AM",
"users": ["user_2"]
}
]
}
}
Limits and batching
- Each notification object should target no more than 1,000 User IDs in its
usersfield (the same limit is documented fordevices). Ifusersholds more than 1,000, the API does not reject the request: it returns a warning and sends the push only to a random subset of those users. - There is no per-account cap on the number of
/createMessageor/createTargetedMessagerequests, so you can send as many requests as your integration needs. - Keep individual requests reasonably small and split very large audiences across several requests. If you need a guaranteed maximum for the number of objects in one
notificationsarray or for the request body size, ask Pushwoosh support — these are not published limits. - Use
transactionIdto protect against duplicates on retry. Pushwoosh stores this identifier for 5 minutes, so a retry sent within that window is ignored; a retry sent later is treated as a new message.
Comments
0 comments
Please sign in to leave a comment.