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. You can see your current tier in your Workspace Settings.
Plan TierMonthly CreditsDescription
Trial1,000Free trial with basic limits
Bronze2,500 - 10,000Starter plans for small teams
Silver10,001 - 100,000Growth plans for scaling teams
Gold100,001 - 500,000Business plans for expanding operations
Platinum500,001 - 2,000,000Scale plans for high-volume operations
Diamond2,000,001 - 20,000,000Advanced plans for large organizations
Titanium20,000,001 - 50,000,000Enterprise plans for maximum scale

​
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
Bronze2120
Silver / Gold10600
Platinum / Diamond201,200
Titanium401,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
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 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
Bronze2100
Silver / Gold4250
Platinum / Diamond5300
Titanium8500

​
Capacity Examples

For identity operations (create, update, delete):
Plan TierDaily CapacityUse Case
Trial~144,000 operations/dayBasic account management
Bronze~144,000 operations/daySmall team setup
Silver / Gold~360,000 operations/dayGrowing organization
Platinum / Diamond~432,000 operations/dayLarge team management
Titanium~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
Bronze< 110
Silver / Gold150
Platinum / Diamond175
Titanium2100

​
Run Outputs

Rate limits for polling run results via /v1/runs/{run_uid}/outputs. These limits support realistic polling patterns for customers who prefer polling over callbacks.
Plan TierMax Requests/SecondMax Requests/MinuteRationale
Trial< 130Supports 2 concurrent runs @ 10s polling interval
Bronze160Supports 2 concurrent runs with more aggressive polling
Silver / Gold2.5150Supports 5 concurrent runs @ 10s polling interval
Platinum / Diamond5300Supports 10 concurrent runs @ 10s polling interval
Titanium10600Supports 15 concurrent runs @ 10s polling interval
These limits are aligned with concurrent execution limits. For example, with a Silver/Gold plan (5 concurrent runs), you can poll all active runs every 10 seconds with comfortable headroom.

​
Capacity Examples

Plan TierPolling CapacityUse Case
TrialPoll 2 runs every 10sBasic polling during development
BronzePoll 2 runs every 10s with headroomSmall-scale polling
Silver / GoldPoll 5 runs every 10s, or 1 run every 4sTeam polling operations
Platinum / DiamondPoll 10 runs every 10sMulti-workspace polling
TitaniumPoll 15 runs every 10sEnterprise-scale polling
Implementation Details:
  • Rate limit type: Per-workspace, per-minute
  • Error response: Standard 429 with X-RateLimit-Type: /v1/runs/outputs
  • Headers include X-RateLimit-Remaining for visibility

​
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 / Bronze22
Silver / Gold53
Platinum / Diamond105
Titanium158

​
Capacity Examples

For async automations with concurrent execution:
Plan TierEstimated Daily CapacityUse Case
Trial / Bronze~50,000-100,000 records/dayBasic automation
Silver / Gold~200,000-500,000 records/dayTeam automations
Platinum / Diamond~500,000-1,000,000 records/dayLarge-scale automation
Titanium1,000,000+ records/dayEnterprise automations
Example: With a Platinum or Diamond 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

​
Engagement Mode Rate Limits

For identities configured in engagement mode, a separate rate-limiting system applies. These limits are based on the number of engagement identities in your workspace, not your credit-based plan tier.
Engagement mode identities are designed for LinkedIn automation workflows that don’t consume credits. Because of this, dedicated rate limits ensure fair usage across all users.

​
Rate Limits by Identity Count

Identities/v1/actions (calls/min)/v1/actions (calls/sec)/v1/identities/v1/workspacesMax Concurrent RunsDaily API LimitBatches per Run
1–50250.4100102720,0002
51–200500.83003063,600,0006
201–1,0002504.2600601214,400,00012
1,001–5,0001,25020.81,0001002072,000,00020
5,001–10,0002,400 (cap)401,0001002072,000,00020
As your engagement identity count grows, your rate limits automatically scale up to support higher volumes.

​
Understanding Engagement Limits

  • /v1/actions: Controls how many action requests you can make per minute/second
  • /v1/identities: Maximum operations per minute for identity management
  • /v1/workspaces: Maximum workspace info requests per minute
  • Max Concurrent Runs: Number of async runs that can execute in parallel
  • Daily API Limit: Total API calls allowed per day across all endpoints
  • Batches per Run: Maximum batches allowed per async run
If you have both engagement identities and a credit-based plan, the higher limit between the two systems applies for each endpoint.

​
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)"
  }
}

​
Other Limit Errors to handle

In addition to internal Edges rate limits, you may encounter LinkedIn-originated rate limits, which we proactively detect and surface with standardized errors. These are not caused by Edges infrastructure but reflect LinkedIn’s own protective mechanisms.
Error Typestatus_codeerror_labelOrigin
Internal429n/aEdges API
Detected429LIMIT_REACHEDLinkedIn (with protection logic in Edges)
Passive429STATUS_429LinkedIn (propagated, no guardrails)
Handling Strategy (All Cases):
  • Implement exponential backoff before retrying
  • Monitor for recurring errors per identity
  • Avoid retrying immediately and let an extended cooldown period elapse
LIMIT_REACHED errors are triggered by Smart Limits — Edges tracks LinkedIn activity on a 24-hour sliding window to prevent account restrictions. Learn more about Smart Limits.
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.

​
Plan-Specific Considerations

​
Trial and Bronze

  • Focus on development and testing
  • Use async mode for production workloads
  • Monitor usage closely to avoid interruptions

​
Silver, Gold, Platinum, and Diamond

  • Suitable for production workloads
  • Balance between real-time and async execution
  • Consider upgrading for higher volume needs

​
Titanium

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