Skip to contentSkip to navigationSkip to topbar
Twilio Docs
Page tools
On this page
Looking for more inspiration?Visit the

Twilio Communications API

(new)

Beta

Twilio Communications API is currently available as a Private Beta product and the information contained in this document is subject to change. You acknowledge and agree that your use of Twilio Communications API is subject to the terms of the Services in Private Beta(link takes you to an external page). This means that some features are not yet implemented and others may be changed before the product is declared as Generally Available. Private Beta products are not covered by the Twilio Support Terms or Twilio Service Level Agreement.

(new)

Beta

Request access to the private beta through this form(link takes you to an external page).

Overview

overview page anchor

This guide will help you get started with Twilio Communications API. We'll walk through the functionality, review API request samples, and outline the steps for sending personalized messages.

The API enables you to start with basic requests and scale to complex, multichannel production workloads.

  • Send in bulk and reduce system load: Send a single outbound message to one recipient or to up to 10,000 recipients in a single API request. You can store recipient details and create recipient groups to handle campaigns that target as many as 1 million recipients.
  • Send across channels: Send messages across SMS, MMS, RCS, or WhatsApp.
  • Content personalization: Personalize individual messages inline with your API request to Twilio. You can use and reuse details you've stored about your users to personalize messages across channels.
  • Send rich content across channels: Continue to use Twilio's content templates for WhatsApp, RCS and SMS. For channels that don't require template approvals, you can also send rich content, such as cards, directly in your API request without first creating a template.

Requests to the Twilio Communications API use the same basic structure as your existing Messaging API requests. Include the to, from, and content (message body) parameters in the request. The key difference is that the Twilio Communications API expects a JSON payload instead of form-encoded data.

1
{

2
 "to": [{...}],

3
 "from": {...},

4
 "content": {...}

5
}

When you make a request that could create multiple resources, such as sending messages, the API responds with a 202 Accepted status code and an empty response body. These requests are processed asynchronously: the API validates your input and completes the operation in the background. The response headers include an operationId, which you can use to check the status of your request.

Limitations

limitations page anchor
  • Requests payload are limited to 10MB.
  • The to array in the Messages endpoint accepts a maximum of 10,000 recipients.
  • Your existing messages per second (MPS) limits still apply.

Next steps

next-steps page anchor