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.

​
Overview

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

Your rate limits are determined by your plan tier, which is based on your monthly credit allocation:
Plan TierMonthly CreditsDescription
Trial1,000Free trial with basic limits
Low2,500 - 10,000Starter plans for small teams
Mid10,000 - 500,000Plans for expanding businesses
High500,000 - 20,000,000Plans for high-volume operations
Highest20,000,000 - 100,000,000Enterprise plans for large organizations

​
API Rate Limits

​
Real-time Operations

The most important rate limits apply to API real-time operation execution. These limits determine how many requests you can make per minute:
Plan TierMax Requests/SecondMax Requests/Minute
Trial160
Low2120
Mid10600
High201,200
Highest402,400

​
Capacity Examples

Assuming an average request duration of 2-3 seconds:
Plan TierEstimated Daily CapacityExample Use Case
Trial~86,400 requests/daySmall-scale testing
Low~172,800 requests/dayIndividual prospecting
Mid~864,000 requests/dayTeam sales operations
High~1,728,000 requests/dayLarge-scale enrichment
Highest~3,456,000 requests/dayEnterprise automation
Example: With a Mid 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

​
Workspace Info

Rate limits for workspace data retrieval via /v1/workspaces:
Plan TierMax Requests/SecondMax Requests/Minute
Trial< 15
Low< 110
Mid150
High175
Highest2100

​
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/actions"
    },
    "message": "Rate limit exceeded (/v1/actions)"
  }
}
This rate limit error response uses a different structure than our standard error format. For details on our typical error responses, see our FAQ and Troubleshooting guide.

​
Plan-Specific Considerations

​
Free and Low Tiers

  • Focus on development and testing
  • Monitor usage closely to avoid interruptions

​
Mid and High Tiers

  • Suitable for production workloads
  • Consider upgrading for higher volume needs

​
Highest Tier

  • Designed for enterprise-scale operations
  • Maximum concurrent execution capabilities
  • Contact support for custom limits if needed

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