Rate Limits
Overview
The smenso API enforces rate limits to ensure fair usage, platform stability, and a consistent experience for all workspaces. Rate limits apply to all API models (JSON, XML, and Reporting).
Current limits
| Scope | Limit | Window |
|---|---|---|
| Per API token | {z.B. 100 requests} | {z.B. per minute} |
| Per workspace | {z.B. 500 requests} | {z.B. per minute} |
Response headers
| Header | Description |
|---|---|
Retry-After | Number of seconds to wait before retrying |
X-RateLimit-Limit | Maximum number of requests allowed in the current window |
X-RateLimit-Remaining | Number of requests remaining in the current window |
X-RateLimit-Reset | Timestamp (Unix) when the rate limit window resets |
Handling rate limits
Respect the Retry-After header
Retry-After headerWhen you receive a 429 response, wait for the duration specified in the Retry-After header before making the next request.
Use exponential backoff
If no Retry-After header is provided, apply exponential backoff:
- Wait 1 second → retry
- Wait 2 seconds → retry
- Wait 4 seconds → retry
- Wait 8 seconds → retry
- Cap at 30 seconds
Optimize your integration
- Batch operations where possible instead of sending individual requests for each record.
- Cache responses that don't change frequently (e.g., timezone lists, flavor configurations).
- Spread requests over time rather than sending bursts.
- Use the Reporting API for bulk data extraction instead of iterating over individual records with the Integration API.
Rate limits and async tickets
Submitting a batch request (e.g., 100 tasks in one POST) counts as a single request against the rate limit. Subsequent status polling calls each count as individual requests - use the backoff strategy described in Integration Tickets to avoid hitting rate limits during polling.
Best practices
- Monitor your request volume and stay well below the limits during normal operation.
- Implement proper
429handling from the start - don't wait for production issues. - Log rate limit events so you can identify and address spikes.
- If your use case requires higher limits, contact smenso support
Updated 14 days ago
