Skip to main content

Documentation Index

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

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

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 TierMonthly CreditsMax Requests/SecondMax Requests/Minute
TrialUp to 1,000160
Bronze1 - 10,0002120
Silver10,001 - 100,00010600
Gold100,001 - 500,00010600
Platinum500,001 - 2,000,000201,200
Diamond2,000,001 - 20,000,000201,200
Titanium20,000,001 - 50,000,000402,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 TierEstimated Daily CapacityExample Use Case
Trial~86,400 requests/daySmall-scale testing
Bronze~172,800 requests/dayIndividual prospecting
Silver / Gold~864,000 requests/dayTeam sales operations
Platinum / Diamond~1,728,000 requests/dayLarge-scale enrichment
Titanium~3,456,000 requests/dayEnterprise 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 TierMax Requests/SecondMax Requests/Minute
Trial< 15
Bronze< 110
Silver150
Gold150
Platinum175
Diamond175
Titanium2100

​
Best Practices

​
Optimizing for Rate Limits

  1. Implement Exponential Backoff: When you hit rate limits, wait before retrying with increasing delays.
  2. 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:
  1. Review your implementation design for optimization opportunities
  2. Consider upgrading your plan for higher limits
  3. Contact support for custom enterprise solutions
For detailed information about your current plan’s limits, check your workspace dashboard or contact our support team.