The Propal API uses a sliding window rate limiter. Each organization has a maximum number of requests allowed per hour. The window slides continuously with no fixed reset time.Documentation Index
Fetch the complete documentation index at: https://docs.propal.io/llms.txt
Use this file to discover all available pages before exploring further.
Limits
| Limit | |
|---|---|
| Requests / hour | 1000 |
Rate limits apply per organization, not per API key. If you have multiple API keys for the same organization, they share the same limit.
Response headers
Every API response includes rate limit information in the headers:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the current window. |
X-RateLimit-Remaining | Requests remaining in the current window. |
X-RateLimit-Reset | Unix timestamp when the window resets. |
When you’re rate limited
When you exceed your limit, the API returns a429 Too Many Requests response:
Retry-After header indicating how many seconds to wait:
Best practices
Monitor your usage
Check
X-RateLimit-Remaining in response headers. If it’s dropping fast, slow down your requests.Use bulk operations
Fetch up to 100 items per request with
limit=100 instead of making many small requests.Cache responses
Cache API responses locally when the data doesn’t change frequently (e.g., templates, themes, organization details).
Implement backoff
When you receive a
429, wait for the Retry-After duration before retrying. Don’t retry immediately.