Skip to main content

CronDB API Best Practices: Rate Limits, Pagination, and Caching

· 2 min read
Alex Ciachir
Alex Ciachir
Founder, CronDB

Whether you're enriching leads in your CRM, building a custom dashboard, or automating prospecting workflows, these patterns will help you get the most from the CronDB API.

Authentication​

All API requests require a Bearer token. Generate one from your API Keys page.

curl -H "Authorization: Bearer YOUR_API_KEY" \
     https://api.crondb.com/v1/leads?country=US&limit=10

Respect Rate Limits​

Each plan has daily query limits. The API returns X-RateLimit-Remaining headers so you can track usage proactively. When you hit the limit, you'll receive a 429 status — implement exponential backoff rather than retrying immediately.

Use Pagination Efficiently​

The /v1/leads endpoint supports limit and offset parameters. For large result sets:

  • Start with smaller page sizes (25-50) to reduce response times
  • Use the total field in the response to calculate total pages
  • Cache results client-side to avoid re-fetching pages

Filter Early, Process Less​

The API supports extensive filtering: country, industry, technology, intent score, and more. Apply filters at the API level rather than fetching everything and filtering client-side.

# Instead of fetching all leads and filtering in code:
curl "https://api.crondb.com/v1/leads?country=US&industry=technology&min_score=70&limit=50"

Webhook-Driven Architecture​

Instead of polling for changes, set up webhooks to receive real-time notifications when domains matching your criteria appear or change. This reduces API calls and improves response time.

Batch Operations​

For enrichment workflows, use the batch endpoints where available:

  • /v1/enrichment/batch-check — check data completeness for up to 50 domains at once
  • /v1/leads/lookalikes/bulk — find lookalikes for multiple seed groups

Error Handling​

Always handle these status codes:

  • 401 — Invalid or expired token
  • 403 — Feature not available on your plan
  • 404 — Domain not found in our database
  • 429 — Rate limit exceeded
  • 500 — Server error (retry with backoff)

Check our API Reference for complete endpoint documentation with code examples in Python, Node.js, and Ruby.