> 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/data-api-sdk/historical-data-and-backfill/provider-rate-limits-backfill.md).

# Why am I hitting rate limits during a backfill?

A `429` carrying a provider rate-limit message means the **upstream provider's per-user quota is exhausted**, not a Terra limit. Terra's own [API rate limit](https://docs.tryterra.co/reference/health-and-fitness-api/rate-limits) is very lenient.

Provider quotas vary:

* **Fitbit** is the most restrictive, at roughly 150 requests per user per hour.
* **Withings** is also restrictive.
* **Apple Health** has no provider-side request limit.
* **WHOOP**: one Terra request fans out into several WHOOP calls (activity/athlete = 1, sleep = 2, daily = 4), and webhook-triggered fetches count too, so polling plus backfills exhaust the quota quickly.

To mitigate:

* Prefer **webhooks over polling**.
* Avoid concurrent or repeated requests for the same user, and retry only after the window resets.
* Set `retry_if_rate_limited=true` so Terra retries and delivers all data later.
* Use `to_webhook=true` for large requests. A `504` is expected on large synchronous transfers because of a 30s cutoff.

For **Strava**, Terra has no direct partnership, so limits are tied to the credentials you obtained from Strava yourself. **Request an increase directly from Strava**, which they often grant.


---

# 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/data-api-sdk/historical-data-and-backfill/provider-rate-limits-backfill.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.