Skip to main content

Rate limiting

Pulsus APIs apply rate limits to help maintain platform stability and availability. Limits vary by contracted plan and, for some resource-intensive APIs, by API type.

APIInventory PlusManagementPro
Signal & Location1 req/min10 req/min20 req/min
All other APIs10 req/min30 req/min60 req/min

* Each API call is counted as one request.

Rate limits apply to the account as a whole, including the combined requests made by all tokens and integrations associated with it.

When the limit is reached​

When the rate limit is exceeded, the API returns:

429 Too Many Requests

Wait before retrying the request. If a Retry-After header is provided, use it to determine when to retry.

  • Avoid unnecessary or repetitive requests.
  • Use pagination and filters whenever available.
  • Implement retries with exponential backoff.
  • Respect the Retry-After header when provided.

Need a higher limit?​

If your integration requires a higher request volume, contact Pulsus support to review the limits available for your plan.