POST /api/v2/message/schedule
Creates a new scheduled message that will be sent at the specified time.
Messages can be sent to multiple phone numbers OR to a Dialpad channel.
Added on Dec 5, 2025 for API v2.
Rate limit: 1200 per minute.
Servers
- https://dialpad.com/
- https://sandbox.dialpad.com/
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
timezone |
Null | No |
Timezone name (e.g., 'America/Los_Angeles'). Default value: "US/Pacific" |
start_date |
Integer | No |
Unix timestamp for when to send the message (must be 10+ minutes in future). |
text |
Null | No |
The message text content. |
is_bulk |
Boolean | No |
Whether this is a bulk message (affects rate limiting and delivery). Maximum of 50 recipients. Default value: false |
channel_hashtag |
Null | No |
[single-line only] The hashtag of the channel which the message is scheduled for. |
from_number |
Null | No |
The personal phone number to use as the sender (must belong to the user). |
to_numbers[] |
Array | No |
Up to 50 List of E164-formatted phone numbers to send messages to. |
user_id |
Integer | No |
The ID of the user who should be the sender. If not provided, defaults to the authenticated user. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.