Rate Limits

Captain Data implements rate limits to ensure fair usage and optimal performance for all users. Understanding these limits helps you design efficient automations and avoid interruptions. Rate limits are applied at multiple levels:

API Endpoints: Per-minute limits on specific API calls
Daily Quotas: Total daily usage limits based on your plan

Each plan includes a daily quota that represents your total usage allowance. This quota is consumed by all API calls across your workspace.

Plan Tiers and Rate Limits

Your rate limits are determined by your plan tier, which is based on your monthly credit allocation:

Plan Tier	Monthly Credits	Max Requests/Second	Max Requests/Minute
Trial	Up to 1,000	1	60
Bronze	1 - 10,000	2	120
Silver	10,001 - 100,000	10	600
Gold	100,001 - 500,000	10	600
Platinum	500,001 - 2,000,000	20	1,200
Diamond	2,000,001 - 20,000,000	20	1,200
Titanium	20,000,001 - 50,000,000	40	2,400

Check your subscription page in Captain Data to see your current plan tier and monthly credit allocation.

Capacity Examples

Assuming an average request duration of 2-3 seconds:

Plan Tier	Estimated Daily Capacity	Example Use Case
Trial	~86,400 requests/day	Small-scale testing
Bronze	~172,800 requests/day	Individual prospecting
Silver / Gold	~864,000 requests/day	Team sales operations
Platinum / Diamond	~1,728,000 requests/day	Large-scale enrichment
Titanium	~3,456,000 requests/day	Enterprise automation

Example: With a Silver or Gold tier plan (600 requests/minute), you can:

Enrich ~864,000 people profiles per day
Process ~36,000 profiles per hour
Handle ~600 concurrent enrichment requests

Quotas

Rate limits for quota and billing data retrieval via /quotas:

Plan Tier	Max Requests/Second	Max Requests/Minute
Trial	< 1	5
Bronze	< 1	10
Silver	1	50
Gold	1	50
Platinum	1	75
Diamond	1	75
Titanium	2	100

Best Practices

Optimizing for Rate Limits

Implement Exponential Backoff: When you hit rate limits, wait before retrying with increasing delays.
Monitor Your Usage: Track your API consumption to stay within limits.

Handling Rate Limit Errors

When you exceed rate limits, you’ll receive a 429 Too Many Requests response.

{
  "error": {
    "code": 429,
    "status": "Too Many Requests",
    "details": {
      "Retry-After": "60",
      "X-RateLimit-Limit": "2",
      "X-RateLimit-Reset": "1754402101",
      "X-RateLimit-Type": "/v1/people/enrich"
    },
    "message": "Rate limit exceeded (/v1/people/enrich)"
  }
}

This rate limit error response uses a different structure than our standard error format. For details on our typical error responses, see our Error Reference.

Monitoring and Alerts

Track your rate limit usage through:

API response headers
Dashboard analytics
Webhook notifications for quota warnings

Getting Help

If you consistently hit rate limits or need higher limits:

Review your implementation design for optimization opportunities
Consider upgrading your plan for higher limits
Contact support for custom enterprise solutions

For detailed information about your current plan’s limits, check your workspace dashboard or contact our support team.

Getting Started

People

Companies

Workspace

Plan Tiers and Rate Limits

Capacity Examples

Quotas

Best Practices

Optimizing for Rate Limits

Handling Rate Limit Errors

Monitoring and Alerts

Getting Help

​Plan Tiers and Rate Limits

​Capacity Examples

​Quotas

​Best Practices

​Optimizing for Rate Limits

​Handling Rate Limit Errors

​Monitoring and Alerts

​Getting Help

Plan Tiers and Rate Limits

Capacity Examples

Quotas

Best Practices

Optimizing for Rate Limits

Handling Rate Limit Errors

Monitoring and Alerts

Getting Help