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.
| API | Inventory Plus | Management | Pro |
|---|---|---|---|
| Signal & Location | 1 req/min | 10 req/min | 20 req/min |
| All other APIs | 10 req/min | 30 req/min | 60 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.
Recommended practices
- Avoid unnecessary or repetitive requests.
- Use pagination and filters whenever available.
- Implement retries with exponential backoff.
- Respect the
Retry-Afterheader 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.