Skip to main content

​
1. Edges Smart Limits

Edges protects your clients’ LinkedIn accounts with our unique Smart Limits system. By using Edges exclusively, clients can run a high volume of actions without issues. These limits help stay within LinkedIn’s daily action caps, preventing account restrictions.
Smart Limits operate on a 24-hour sliding window.
What happens when the limit is reached? In real-time mode, requests will fail with a rate limit error. In async or schedule modes, tasks will be postponed and automatically resume once the limit is freed up.
Example Over 24 hours: If it’s Wednesday at 2 PM, Edges checks the past 24 hours for any activity:
  • If the limit is hit (e.g., 1000/1000 actions), no new tasks are launched in async/schedule modes, or requests fail immediately in real-time mode.
  • We periodically check to see if the limit is cleared, e.g., at 3 PM, there might be 100 actions freed up.
  • The available actions may vary depending on when the limit was last checked.
Edges only tracks actions performed within the platform, not manual actions on LinkedIn or using other automation tools.

​
How Smart Limits Work

Limits are per-action, per-identity. Each LinkedIn action (e.g., linkedin-connect-profile, salesnavigator-search-metrics) has its own daily limit tracked separately for each identity.
ConceptExplanation
Per-actionHitting the limit on salesnavigator-search-metrics doesn’t affect linkedin-extract-people
Per-identityEach identity has its own limit counter for each action
24-hour sliding windowLimits reset gradually, not all at once at midnight
Example: If Identity A hits its linkedin-connect-profile limit, it can still run linkedin-extract-people. Identity B is unaffected.

​
Auto Mode and Rate Limits

When using identity_mode=auto, Edges distributes requests across all available identities. If all identities in your pool hit their Smart Limit for a specific action, you’ll see: 
{
  "label": "LIMIT_REACHED",
  "message": "Daily limit reached for linkedin.",
  "error": "all integration identities are exhausted",
  "postponed_until": "2025-12-23T15:15:42.523Z"
}
What this means:
  • Every identity in your pool has reached its daily limit for this specific action
  • The task is postponed until postponed_until (when limits start freeing up)
  • Other actions may still work (limits are per-action)
Solutions:
  • Add more identities to your pool
  • Use identity_mode=managed to access Edges’s account pool
  • Wait for postponed_until — async tasks automatically retry

​
Checking Your Current Limits

Use the Get Identity Limits endpoint to check real-time usage: 
GET /v1/identities/{identity_uid}/actions/{action_slug}/limits
Example: Check salesnavigator-search-metrics limits for a specific identity: 
curl -X GET "https://api.edges.run/v1/identities/your-identity-uid/actions/salesnavigator-search-metrics/limits" \
  -H "X-API-Key: your-api-key"
This endpoint evaluates limits in real-time, which is resource-intensive. Use it sparingly — don’t poll continuously. It is rate limited along with other identity management operations. Check the Rate Limits documentation for details.

​
2. Key Points for Avoiding LinkedIn Restrictions

When implementing Edges for LinkedIn automation, it’s crucial to inform your users about a few key actions to prevent account restrictions. Key steps to follow:
StepAction
1. Avoid Multiple Automation ToolsAdvise against using multiple automation tools simultaneously to prevent LinkedIn from flagging the account for suspicious activity.
2. Match Timezone SettingsEnsure the timezone selected in Edges matches the user’s actual location or VPN country.

​
Avoid Using Multiple Automation Tools Simultaneously

Using multiple automation tools at once with Edges can cause issues.
  • Why? Many automation tools don’t manage IP addresses properly, which could trigger flags on LinkedIn. When using multiple tools, LinkedIn may detect activity from different sources, increasing the likelihood of restrictions.
  • The result: LinkedIn might flag the account for suspicious activity, potentially resulting in restrictions.

​
Ensure Timezone Settings Match

The timezone selected in Edges must match the country where you’re logging into LinkedIn.
  • Why it matters: The timezone field provisions a proxy IP matching that timezone/country. If the timezone in your Edges identity doesn’t align with your LinkedIn login location, LinkedIn may restrict your account.
  • What to do: Always check that the timezone in your Edges identity matches the country where you’re logging into LinkedIn to avoid being flagged.

​
VPN Use: Match Locations Carefully

Using a VPN can be helpful but needs careful management.
  • Best practice: The country in your VPN should match the timezone set in Edges. If there’s a mismatch, LinkedIn might flag your activity as suspicious.
  • Tip: Double-check that the timezone in Edges matches your VPN’s location, or disconnect the VPN when accessing LinkedIn to avoid issues.

​
What to Do if Your Client Gets a LinkedIn Restriction?

  • Don’t worry! Restrictions are usually temporary. ⏳
  • Steps to follow:
    1. Are other automation tools running alongside Edges?
    2. Does the timezone setting in Edges match the user’s actual location?
    3. If using a VPN, does the VPN location match Edges’s timezone setting?

​
3. Best Practices

  • Scale your efforts: Use multiple identities and the identity_mode=auto feature to manage higher action volumes while staying within LinkedIn’s limits.
  • Avoid overloading: Space out actions over time to improve efficiency and avoid triggering restrictions.
  • Monitor activity: Regularly track identity usage to prevent exceeding limits unexpectedly.
  • Choose the right execution mode: Use real-time mode for immediate results, async mode for large batches, and schedule mode for time-based automation.
By following these guidelines, you can ensure smooth LinkedIn automation without restrictions!

​
4. LinkedIn Limits

​
LinkedIn Commercial Limits

All limits are based on a 24-hour sliding window, meaning they reset every 24 hours.
A single limit may be consumed by multiple actions. For example, LK_PROFILE_ENRICHMENTS can be consumed by messaging or connection actions — not just profile extraction. Use the Get Identity Limits endpoint to see all limits that apply to a specific action.
Limit Name (Per Day)SlugValue LinkedIn/Sales NavigatorPlatformInfoAction Link
Maximum connection requestsLK_CONNECTION_REQUEST25/30LinkedIn, Sales NavigatorClassic accounts can send up to 100 connection requests per week.Connect LinkedIn Profile, Connect Sales Navigator Profile
Maximum messages sentLK_MESSAGES_SENT50/250LinkedIn, Sales NavigatorMessage LinkedIn Profile
Maximum profile visitsLK_PROFILE_VISITS80/500LinkedIn, Sales NavigatorRemember that manual visits also count. For Sales Navigator, use the Visit Sales Navigator Profile Action to increase the limit.Visit LinkedIn Profile, Visit Sales Navigator Profile
Maximum contact infoLK_GET_CONTACT_INFO250LinkedIn, Sales NavigatorExtract LinkedIn Contact
Maximum search peopleLK_SEARCH_PEOPLE—/5,000Sales NavigatorSearch Sales Navigator People
Maximum event invitations sentLK_EVENT_INVITATIONS_SENT100LinkedInInvite People to LinkedIn Event
Maximum profile enrichmentsLK_PROFILE_ENRICHMENTS25,000LinkedInExtract LinkedIn People Profile
Maximum company enrichmentsLK_COMPANY_ENRICHMENTS10,000LinkedInExtract LinkedIn Company Profile
Maximum search saved peopleLK_SEARCH_SAVED_PEOPLE—/5,000Sales NavigatorSearch Sales Navigator Saved People
Maximum search companyLK_SEARCH_COMPANY—/5,000Sales NavigatorSearch Sales Navigator Companies
Maximum search saved companyLK_SEARCH_SAVED_COMPANY—/5,000Sales NavigatorSearch Sales Navigator Saved Companies

​
LinkedIn Usage Limits

Limit Name (Per Day)Value LinkedIn/Sales NavigatorPlatformInfoAction Link
Maximum Search LinkedIn People300 searches/monthClassic AccountsUsers may encounter a restriction after 300 searches in a month.Search LinkedIn People
Maximum Search LinkedIn PeopleUnlimitedSales Navigator AccountsNo search limit.Search LinkedIn People
Maximum Search Sales Navigator PeopleVaries based on account activitySales Navigator Accounts1 search page = 1 API call (each page contains 25 profiles, max 100 pages x 25). Example: 100 results = 4 pages = 4 API calls.Search Sales Navigator People
Maximum Search Sales Navigator Company Employees500 companies every 2 hours (w/ max 25 employees per company)Sales Navigator AccountsIf max employee results are set to 250 → 2 companies every 2 hours.Search Sales Navigator Company Employees
Maximum Extract LinkedIn Connections30,000 connections per dayClassic Accounts, Sales Navigator AccountsExtract all connections at once and set to repeat, ensuring only new, recent connections are captured.Extract LinkedIn Connections
Space out searches to avoid hitting your limits too quickly.
Use identity_mode=auto for automatic load distribution. If you hit rate limits, take a 24-hour break, and/or add more identities, and/or use identity_mode=managed.

​
Limit Reached Errors

While Edges protects your clients’ LinkedIn accounts with Smart Limits, you may still see 429 errors originating from different sources. Here’s how to identify and handle them.
Error Typestatus_codeerror_labelSourceHandling Recommendation
Edges Rate Limit429N/AEdges APIWait for Retry-After, apply exponential backoff
LinkedIn (Guarded)429LIMIT_REACHEDLinkedInWait at least 24h, retry once usage drops
LinkedIn (Raw)429STATUS_429LinkedInApply exponential backoff, monitor identity health
Best Practices:
  • Always implement retry with exponential backoff (e.g. 30s → 60s → 120s…)
  • Use identity rotation or identity_mode=auto to spread traffic or rely on identity_mode=managed to let Edges handle it (higher credits consumption)
  • Use async or schedule modes for large workloads to avoid real-time limits (limits are managed on our side)
For more details on handling errors, refer to our Error Reference.