Requires authentication — see Authentication.
Sends a new Notification depending on the type of communication channel. you want to send (SMS, Email, RCS, WhatsApp).The channel parameter allows us to differentiate the type of communication channel between SMS, WhatsApp, Email, or RCS. That's why only this endpoint is used for the send of Notification because the channel help us to send each type of communication channel.
This is the single endpoint behind the unified Messaging API guide (covering text, media, location, contacts, and interactive messages), and is also used by the channel-specific sending tutorials: Sending Outbound SMS, Sending Email, Sending RCS, Text Message Template, and Media Message Template.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
This endpoint limits how many requests you send in a time window. The response headers show your remaining quota and reset time.
When you exceed the limit, you must wait until the current window ends. After the window resets, you send requests again.
Example limit: 2 requests every 300 seconds (5 minutes).
| Constraint | Value | Description |
|---|---|---|
| Rate limit | 2 requests / 300 seconds | A 3rd request within the 5-minute window returns HTTP 429. |
If you send a third request within 5 minutes, the endpoint returns HTTP 429. The response body includes "errors": { "reason": "Too Many Requests" }.
After the required time elapses, the request counter resets to 2. You send two more requests during the next 5-minute window.
You use these response headers to check your quota:
ratelimit-limit: 2
ratelimit-policy: 2;w=300
ratelimit-remaining: 1
ratelimit-reset: 5m0s- ratelimit-limit: Returns the request limit for the current time window.
- ratelimit-remaining: Returns the remaining quota in the current window.
- ratelimit-reset: Returns the time remaining in the current window, in seconds.
- ratelimit-policy: Returns the quota policy, such as
2;w=300for 2 requests in 300 seconds.