Please Wait...
Understand API limits and best practices.
API Rate Limits help ensure fair usage, platform stability, and reliable performance for all developers using the SPRL REST APIs. Each API Key is subject to request limits based on your account, subscription, and the API service being used.
If your application exceeds the permitted request rate, additional requests may be temporarily rejected until the limit resets.
Each API request counts towards the usage allowance assigned to your API Key. The permitted request rate depends on your account and the API being accessed.
| Factor | Description |
|---|---|
| API Key | Rate limits are applied to each generated API Key. |
| Subscription Plan | Available request capacity may vary depending on your plan. |
| API Service | Different APIs may have different request limits. |
| Time Window | Limits are measured over a defined period before resetting. |
You can view the configured rate limit for each API Key from:
Dashboard → API & Services → HTTP REST API Keys
Each API Key displays its configured request limit, allowing you to monitor the capacity available for your application.
If your application exceeds its allowed request rate, additional requests may be rejected until the current rate limit window resets.
| Situation | Expected Behaviour |
|---|---|
| Within the allowed limit | Requests are processed normally. |
| Rate limit exceeded | Additional requests may be temporarily rejected. |
| Limit window resets | Your application can resume sending requests. |
| Recommendation | Benefit |
|---|---|
| Cache frequently used data | Reduces unnecessary API requests. |
| Batch application processes | Improves efficiency during large operations. |
| Retry only when necessary | Prevents repeated failed requests. |
| Monitor application logs | Helps identify excessive API usage. |
| Issue | Possible Solution |
|---|---|
| Too many requests | Reduce request frequency and wait for the rate limit window to reset. |
| Unexpected request spikes | Review your application for duplicate or repeated API calls. |
| Background jobs exceed limits | Distribute requests over time instead of sending them simultaneously. |
| Application slows down after retries | Implement delayed retries with exponential backoff. |
Yes. Protected API services are subject to request limits appropriate for the service and your account.
Yes. The configured limit may vary depending on the API Key and your account configuration.
Reduce the request rate, optimise your application, and retry after the current limit window resets.
Use caching, avoid duplicate requests, batch operations where possible, and monitor your application's API usage.
Our support team is always happy to assist you.
We use cookies to improve your experience, analyse traffic, and personalise content. By clicking “Accept”, you consent to the use of cookies as described in our Cookie Policy .
Accept cookies Read our Cookie Policy
