Rate Limits

BigPanda enforces rate limits to keep the platform healthy for every organization. Limits are not uniform across the API — each endpoint defines its own limit, and some endpoints add further caps such as a maximum number of items per request.

Check the endpoint reference

Because limits differ per endpoint, the specific rate limit for an endpoint is documented on that endpoint in the API reference. Before you build against an endpoint, confirm the following in its reference:

The request rate limit, for example requests per second or per minute.

Any per-request cap, for example the maximum number of items in a single call.

Any longer-window limit, for example a weekly cap.

When you exceed a limit

When a request exceeds an endpoint's rate limit, BigPanda returns 429 Too Many Requests. To handle it:

Retry after the interval indicated in the response.

Use exponential backoff rather than retrying immediately.

Slow your request rate or polling frequency to stay under the limit. See Best practices.

General guidance

Spread requests over time instead of sending them in bursts.

Use filtering and pagination to reduce the number of calls you need. See Pagination.

When polling an asynchronous job, wait between status checks. See Asynchronous operations.

Next steps

Best practices: Build in retries and backoff.

Errors and troubleshooting: Diagnose a 429 response.

Pagination: Reduce call volume on large datasets.

Check the endpoint reference#

When you exceed a limit#

General guidance#

Next steps#

Check the endpoint reference

When you exceed a limit

General guidance

Next steps