Why am I getting a 403 on generateWidgetSession?
A 403 on this endpoint is usually a configuration or scope issue, not an account block.
A 403 on this endpoint is usually a configuration or scope issue, not an account block. Most rate limits you encounter originate from the upstream providers, which Terra manages on your behalf. See rate limits.
For high-volume launch-day backfills:
1
Keep date ranges to roughly 7 days or fewer per request to stay within provider limits.
2
Pre-connect users.
3
Trigger backfill early. Garmin backfill is async and requires Historical Data Export per user. Poll GET /v2/backfills/status.
If you hit transient errors, share a reproducible cURL and approximate request volume so limits can be reviewed.
PreviousWhy do I get a 400 connection does not support data type error?
NextWhy does the API return "Request is processing" instead of data?
Last updated
Was this helpful?