Exact per-endpoint limits can change by plan and endpoint version. Verify
active limits in your dashboard.
Core behavior
Crustdata applies per-endpoint request limits.
Operationally, you should assume that steady request distribution is safer than bursts, even when total requests per minute look acceptable.
Implementation guidance
To reduce 429 Too Many Requests responses:
- Spread traffic across the full minute instead of burst-sending.
- Use retry logic with exponential backoff and jitter.
- Keep request queues bounded.
- Add circuit breakers around non-critical enrichment flows.
- Monitor request logs and alert on sustained
429 rates.
Client-side best practices
- Centralize throttling in one shared HTTP client.
- Use endpoint-specific concurrency and QPS controls.
- Prioritize business-critical requests when backpressure starts.
- Cache stable results where your workflow allows it.
Rollout checklist
- Start with conservative throughput.
- Increase gradually while tracking latency and error rates.
- Recalibrate limits when you add new endpoints or workflows.
For higher-throughput needs, request custom limits through Crustdata support.
