Skip to main content
Edges 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
  • Concurrent Execution: Limits on parallel automated runs and batch processing
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,000Growth plans for expanding businesses
High500,000 - 20,000,000Scale plans for high-volume operations
Highest20,000,000 - 100,000,000Enterprise plans for large organizations

​
API Rate Limits

​
Real-time Actions

The most important rate limits apply to real-time action execution via /v1/actions/{action-name}/run/live. These limits determine how many requests you can make per minute:
Plan TierMax Requests/SecondMax Requests/Minute
Trial160
Low2120
Mid10600
High201,200
Highest401,200
For async actions, different concurrent execution limits apply (see Concurrent Execution below).

​
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 LinkedIn profiles per day
  • Process ~36,000 profiles per hour
  • Handle ~600 concurrent enrichment requests

​
Identity Management

Rate limits for identity-related operations via /v1/identities (create, update, delete, retrieve):
Plan TierMax Operations/SecondMax Operations/Minute
Trial2100
Low2100
Mid4250
High5300
Highest8500

​
Capacity Examples

For identity operations (create, update, delete):
Plan TierDaily CapacityUse Case
Trial~144,000 operations/dayBasic account management
Low~144,000 operations/daySmall team setup
Mid~360,000 operations/dayGrowing organization
High~432,000 operations/dayLarge team management
Highest~720,000 operations/dayEnterprise identity management

​
Workspace Info

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

​
Concurrent Execution

For async runs via /v1/actions/{action-name}/run/async, we limit the number of concurrent runs and batch processing:
Plan TierMax Concurrent RunsMax Batches per Run
Trial/Low22
Mid53
High105
Highest158

​
Capacity Examples

For async automations with concurrent execution:
Plan TierEstimated Daily CapacityUse Case
Trial/Low~50,000-100,000 records/dayBasic automation
Mid~200,000-500,000 records/dayTeam automations
High~500,000-1,000,000 records/dayLarge-scale automation
Highest1,000,000+ records/dayEnterprise automations
Example: With a High tier plan (10 concurrent runs, 5 batches each):
  • Process ~500,000-1,000,000 records per day
  • Handle complex automations with large results
  • Scale to enterprise-level automation needs

​
Best Practices

​
Optimizing for Rate Limits

  1. Use Async Mode for High Volume: When processing large datasets, use async mode to benefit from concurrent execution limits rather than hitting real-time rate limits.
  2. Batch Your Requests: Group related operations together to minimize API calls.
  3. Implement Exponential Backoff: When you hit rate limits, wait before retrying with increasing delays.
  4. 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
  • Use async mode for production workloads
  • Monitor usage closely to avoid interruptions

​
Mid and High Tiers

  • Suitable for production workloads
  • Balance between real-time and async execution
  • 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.
⌘I