Skip to main content
The Promptster API applies rate limits to ensure fair usage and platform stability.

Limits

Rate limits apply across all endpoints and all API keys from the same IP address.

Rate limit headers

Every API response includes rate limit headers: Example response headers:

429 Too Many Requests

When you exceed the rate limit, the API returns a 429 status code:
The x-ratelimit-reset header tells you when you can resume making requests.

Handling rate limits

Retry with backoff

Check remaining quota

Best practices

Generate multiple candidate keys in a single request (count up to 50) instead of making individual calls.
Artifacts and session data are immutable after generation. Cache them locally to avoid redundant requests.
When polling for completed sessions, 30-60 second intervals are sufficient. Shorter intervals waste quota without meaningful benefit.
Use list endpoints with limit=100 to reduce the number of requests needed to iterate through large result sets.