docs/api-reference/payload-limits.mdx
Payload size limits are an essential functionality for ensuring optimal performance and reliability of the system. They safeguard system resources by preventing oversized payloads from impacting API performance and ensure efficient processing of event triggers.
All event trigger operations have a 512KB (524,288 bytes) payload size limit. This limit applies to the following endpoints:
The payload size limit includes:
When your payload exceeds the 512KB limit, you'll receive an error response indicating the exact size and the limit exceeded.
<Tabs> <Tab title="Single event trigger">For single event triggers (/events/trigger), the error response will be:
{
"statusCode": 413,
"message": "Payload size (524342 bytes) exceeds maximum allowed size of 524288 bytes (512KB). Note: Attachments are excluded from this limit."
}
For bulk event triggers (/events/trigger/bulk), the error response includes the index of the event that exceeded the limit:
{
"statusCode": 413,
"message": "Event at index 1 (workflow: \"workflow-name\") has payload size (524342 bytes) exceeds maximum allowed size of 524288 bytes (512KB). Note: Attachments are excluded from this limit."
}
For broadcast events (/events/trigger/broadcast), the error response will be:
{
"statusCode": 413,
"message": "Payload size (524342 bytes) exceeds maximum allowed size of 524288 bytes (512KB). Note: Attachments are excluded from this limit."
}
Email attachments have a separate size limit: