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. 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.
Request access to the private beta through this form.
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.
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.
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.
to array in the Messages endpoint accepts a maximum of 10,000 recipients.