The server responds to a user’s request by issuing status codes when the request is made to the server. Kindly refer to the table below to further understand the status codes when indicating the success or failure of an API call.
| Status Codes | Description |
|---|---|
| 200 (Successful) | The request was successful, and the server returned the requested data |
| 201 (Created) | The request was successful, and a new resource was created as a result. |
| 204 (No Content) | The request was successful, but there is no content to return (often used for DELETE operations). |
| 400 (Bad Request) | This is due to an invalid request and the server could not process the user's request |
| 401 (Unauthorized) | Authentication is required, but either the user didn't provide it or provided incorrect credentials. |
| (403 Forbidden) | This is likely indicating that your access is blocked by our server, and we're unable to authorize your request. |
| (404 Not Found) | The requested resource could not be found on the server, either because it doesn’t exist, or the URL is incorrect. |
| 405 (Method Not Allowed) | The HTTP method used is not supported by the resource (e.g., trying to POST to a resource that only allows GET). |
| 408 (Request Timeout) | The server timed out waiting for the client to send a request. |
| 429 (Too Many Requests) | The user has sent too many requests in a given amount of time, typically due to rate limiting. |
| 500 (Internal Server Error) | This is a generic error response indicating that the server has encountered an unexpected issue that prevented it from fulfilling the request |
| 501 (Not Implemented) | The server does not support the functionality required to fulfill the request, such as an unsupported HTTP method |
| 502 (Bad Gateway) | The server, while acting as a gateway or proxy, received an invalid response from the upstream server |
| 503 (Service Unavailable) | The server is temporarily unavailable, usually due to maintenance or overload. |
Rate Limit
Twilio enforces rate limits on its API requests. Each Twilio API endpoint has a set of limits that restrict the number of requests a client can make within a defined time period (e.g., requests per minute or hour)."
- The Interactions API has a limit of 20 requests per second per endpoint per account. The API returns an HTTP 429 status when rate limits are exceeded.
- Adding a participant whose identity already belongs to 1000 or more Conversations/Chat Channels will result in an error.
- Maximum length/size of WhatsApp and SMS is1600 Characters.