Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.crustdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Exact per-endpoint limits can change by plan and endpoint version. Verify active limits in your dashboard.
Default rate-limit is 15 requests per minute. Send an email to gtm@crustdata.co to discuss higher limits if needed for your use case.

​
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.

​
Default rate limits by endpoint

The endpoints below currently default to the same baseline request limit.
EndpointDefault rate-limit
/person/search/autocomplete15 requests per minute
/person/professional_network/enrich/live15 requests per minute
/person/professional_network/search/live15 requests per minute
/job/professional_network/search/live15 requests per minute
/job/search15 requests per minute
/web/search/live15 requests per minute
/web/enrich/live15 requests per minute
/dev_platform/enrich15 requests per minute
/employee_review/enrich15 requests per minute
/social_post/professional_network/enrich/live15 requests per minute
/social_post/professional_network/search/live15 requests per minute
/professional_network/search/autocomplete15 requests per minute

​
Implementation guidance

To reduce 429 Too Many Requests responses:
  1. Spread traffic across the full minute instead of burst-sending.
  2. Use retry logic with exponential backoff and jitter.
  3. Keep request queues bounded.
  4. Add circuit breakers around non-critical enrichment flows.
  5. 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.