This article gives you a complete overview of how rate limits work, how to avoid issues, and how to scale safely.
For in-depth technical specifications, check out our Rate Limits documentation.
📌 What Are Rate Limits?
There are two types of rate limits to keep in mind:
API-Platform Rate Limits
These are technical limits applied by Captain Data’s infrastructure. They control how many API calls or automation runs your workspace can trigger over time.
Action-Specific & LinkedIn Limits
These include:
Limits imposed by Captain Data to protect your LinkedIn identity.
LinkedIn’s own usage limits to avoid account restrictions.
⚙️ Platform Rate Limits
Captain Data applies different limits to ensure fair use and prevent infrastructure overload:
API Calls per Minute
Each endpoint has specific thresholds (e.g., get Identities). Too many requests in a short time will trigger a 429 Too Many Requests error.
Concurrent Runs
Your plan determines how many automated Actions can be launched at the same time — especially for async actions and batch processing.
Daily Quotas
Your workspace has a daily usage quota based on your current plan tier. These quotas help manage your total execution volume.
For examples and detailed plan tiers, visit: Rate Limits Overview
👤 Smart Limits for LinkedIn
To avoid LinkedIn restrictions, Captain Data applies Smart Limits that respect LinkedIn’s daily caps.
These limits work on a 24-hour sliding window.
If a limit is hit:
In real-time mode, requests will fail immediately.
In async/schedule mode, tasks will pause and resume automatically once limits are freed.
These Smart Limits are designed to let you run high volumes safely — without risking restrictions.
🧠 Best Practices to Stay Within Limits
To make the most of your plan and avoid interruptions:
Use async mode for large volumes and background processing.
Batch requests instead of sending one call per action.
Distribute execution using multiple identities and identity_mode=auto.
Monitor usage in your dashboard or via API response headers.
Respect timezones to avoid LinkedIn mismatches (especially when using VPNs).
🚫 Common LinkedIn Restrictions (and How to Avoid Them)
Here’s what to watch out for when automating LinkedIn actions:
Limit Type | Example Value | Applies To |
Connection Requests | 25–30/day | LinkedIn/Sales Navigator |
Messages Sent | 50–250/day | LinkedIn/Sales Navigator |
Profile Visits | 80–500/day | LinkedIn/Sales Navigator |
Profile Enrichments | 10,000/day | Captain Data |
Event Invites | 100/day |
These limits are based on LinkedIn’s rules and apply per identity.
Manual actions on LinkedIn also count toward these limits.
Refer to this guide for the full overview.
🧭 How to Monitor & Handle Rate Limits
When a limit is hit, you’ll receive a 429 response with a Retry-After value.
The error will include headers like X-RateLimit-Type and X-RateLimit-Reset to help you retry correctly.
You can track limits via:
API headers
Workspace analytics
Webhook notifications (if enabled)
🛠️ Technical Guides
Full breakdown of quotas, execution limits, and how to optimize usage.
How to stay compliant with LinkedIn limits and prevent identity restrictions.
Need help interpreting your limits or scaling your usage? Contact our support team — we’re happy to help.