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

# 20413: Request Entity Too Large

Log Level: ERROR

## Description

Twilio returned this error because the HTTP request body is larger than the maximum size the endpoint accepts. Reduce the size of the payload and send the request again.

### Possible causes

* The request body includes too much data for the resource you are creating or updating.
* You are sending a large media file, document, or encoded payload in the request body instead of using a supported media URL or upload flow.
* Your application is sending an unexpectedly large JSON, XML, or form-encoded request because of duplicated fields or oversized parameter values.
* A webhook or integration is forwarding a request to Twilio without enforcing payload size limits.

### Possible solutions

* Reduce the size of the request body before sending the request.
* Remove unnecessary parameters, repeated fields, or extra metadata from the payload.
* If you are sending media, use the product's supported media handling method instead of embedding large binary content directly in the request.
* Check your application logs to confirm the final serialized request size your client sends to Twilio.
* Review the API resource you are calling and make sure you are only sending parameters that the endpoint supports.