The Campground API limits the number of requests your API key can make to protect service reliability for all users. If you exceed the limit, requests are rejected until the window resets.Documentation Index
Fetch the complete documentation index at: https://docs.campground.fyi/llms.txt
Use this file to discover all available pages before exploring further.
Limits
| Limit | Value |
|---|---|
| Requests per minute | 100 |
| Scope | Per API key |
Rate limit headers
Every API response includes headers that tell you your current usage:| Header | Description |
|---|---|
X-RateLimit-Limit | Total requests allowed per minute |
X-RateLimit-Remaining | Requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp (seconds) when the window resets |
429 Too Many Requests
When you exceed the limit, the API returns a429 response. The response body follows the standard error format:
X-RateLimit-Reset header to know when you can resume sending requests.
Best practices
- Cache responses. If multiple parts of your integration need the same profile or team data, fetch it once and store it locally rather than making repeated API calls.
- Paginate efficiently. Use the
limitandpageparameters to fetch only the records you need. Avoid fetching all records on every sync cycle if only a subset has changed. - Respect the reset header. When you receive a
429, pause until theX-RateLimit-Resettimestamp rather than retrying immediately. - Use exponential backoff. For transient errors, implement retry logic with exponential backoff to avoid hammering the API during degraded conditions.
- Batch field updates. The
PATCH /profiles/:id/fieldsendpoint accepts up to 100 field values in a single request, so prefer one batched call over many individual updates.