---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/400#article
headline: "400: Bad Request"
url: https://www.twilio.com/docs/api/errors/400
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 400: Bad Request

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when a REST API request cannot be completed because the request is invalid. When a request is unsuccessful, the response includes an exception with the HTTP `status`, a `message`, and, when available, a Twilio-specific `code` and `more_info` value.

### Possible causes

* A required parameter is missing from the request.
* One or more request parameters did not pass validation.
* The resource you are trying to modify has moved into a state that is no longer valid for that operation.

### Possible solutions

* Inspect the response `message`, `code`, and `more_info` fields to identify the exact problem in the request.
* Add any missing required parameters before you retry the request.
* Validate each request value against the endpoint requirements and correct any malformed or unsupported input.
* Verify that the resource exists and is still in a state that allows the requested update.
* Retry the request only after you confirm the request is valid.

#### Additional resources

* [Our API: the basics](/docs/iam/api)
* [Twilio Debugger](/docs/usage/troubleshooting/debugging-your-application)
