> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/webhook/large-payloads-and-chunking/large-payload-chunking-413.md).

# Will Terra retry or chunk a 413 payload for me?

**Terra does not retry with a smaller payload after a `413`.**

There is no fixed size limit on a single webhook (long activities can be tens of MB). Automatic chunking only triggers when an API request spans **more than one calendar month**: a within-month range (for example Dec 1 to Dec 31) is never split regardless of size, and can exceed your host's request limit.

To force splitting, use a range that crosses a month boundary (for example Dec 1 to Jan 31). Each chunk is then capped around 10MB and all chunks share the same `terra-reference` header. See the documented limits in [setting up webhook destinations](https://docs.tryterra.co/health-and-fitness-api/integration-setup/setting-up-data-destinations/webhooks).

To handle large payloads reliably:

* raise the body-size limit on your webhook server and any proxy/ingress in front of it
* narrow the date range per request
* enable the PING / `s3_payload` mechanism that sends a short-lived URL you GET to retrieve the full payload


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/webhook/large-payloads-and-chunking/large-payload-chunking-413.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.