Provider Limits and Restrictions
Understand how Unipile's rate limiter protects your users' accounts, and the limits and restrictions to respect for each provider.
Unipile applies its own rate limiter to protect the accounts connected by your users. Every Methods API request is counted for each connected account and each route, over fixed time windows. When a request exceeds the configured allowance, Unipile rejects it with a 429 Too Many Requests error (api/too_many_requests) before it reaches the provider, so the account is never exposed to the provider's own throttling or anti-abuse checks. Recommended limits are set by default for each provider and can be adjusted in the Dashboard under Configuration → Rate limits. Requests served from cache don't count toward these limits.
The rate limiter does not replace good usage practicesThe rate limiter is a safety net: it caps request volume, but providers also watch behavior that a request counter cannot capture, such as account age and history, activity spread over days and weeks, regular or robotic intervals, reply and acceptance rates, or spam reports. To keep your users' accounts secure, you must still pay attention to the limits and restrictions of each provider, and respect the usage and limits of each one, as described below.
LinkedIn
Key rules
- Limits apply per LinkedIn account and per action. Each action has its own budget: sending invitations doesn't reduce your profile-retrieval budget.
- These are conservative recommendations, not guarantees. LinkedIn doesn't publish its limits. You can go higher at your own risk.
- Act like a human. Spread calls randomly during working hours. Never run actions at fixed intervals or fixed times.
- Ramp up new or inactive accounts. Start low and increase gradually over several weeks. Accounts with fewer than ~150 connections, or recently created ones, may see invitations delayed or not delivered.
- Use real accounts only. LinkedIn detects fake accounts, even without automation.
Recommended limits at a glance
| Action | Free account | Paid account (Premium, Sales Navigator, Recruiter) |
|---|---|---|
| Send invitations (with a note) | ~5 per month | 80–100 per day, ~200 per week |
| Send invitations (without a note) | ~150 per week | 80–100 per day, ~200 per week |
| Retrieve user profiles | ~100 per day | ~100 per day, plus an extra budget with Sales Navigator / Recruiter (details) |
| Search results retrieved | 1,000 profiles per day | 1,000 per day (2,500 with Sales Navigator / Recruiter) |
| Send InMails | Depends on your subscription credits | 30–50 per day recommended. Free InMails to Open Profiles: max 800 per month |
| Poll relations / invitation lists | A few times a day, at random times | A few times a day, at random times |
| Any other action (posts, comments, reactions, company profiles, messages to connections…) | 100 per day | 100 per day |
| Read chats and messages | No limit | No limit |
What happens when you go over
| You receive | Meaning | What to do |
|---|---|---|
429 api/too_many_requests | Unipile's rate limiter stopped the request before it reached LinkedIn. The account is safe. | Wait for the retry-after delay. |
422 cannot_resend_yet | LinkedIn's invitation limit is reached. The same limit applies in the LinkedIn UI. | Stop sending invitations for this account and try again later. |
429 provider/too_many_requests or 500 | LinkedIn throttled the account. | Slow down this account significantly. Repeated hits can trigger automation warnings. |
Details
Invitations
Paid accounts can add a note of up to 300 characters, free accounts up to 200 characters.
When the invitation limit is reached, LinkedIn returns 422 / cannot_resend_yet. This limit is LinkedIn's own: you'll have the exact same limit in the LinkedIn UI. You can check it by trying the same invitation type (with or without a note) in the UI: LinkedIn only shows the error at the last step, so the process can look successful until the end.
Retrieve user profiles
This budget covers profile visits and ID conversions with Get a User Profile: ~100 profiles per account per day.
If the account has Sales Navigator or Recruiter, you can retrieve additional profiles each day by setting the variant parameter to linkedin_sales_navigator or linkedin_recruiter. Recruiter Lite has an official limit of 2,000.
Search
There are two separate limits:
- Per-search cap (LinkedIn limit): a single search query returns at most 1,000 profiles on standard LinkedIn, and 2,500 on Sales Navigator / Recruiter (Company search on Sales Navigator stays at 1,000). Even if the UI shows more total results, LinkedIn only returns the first ones. To retrieve all results, narrow your query with filters and run several searches.
- Daily usage (Unipile recommendation): retrieve at most 1,000 profiles per day (standard) or 2,500 (Sales Navigator / Recruiter) in total. This counts the result lines actually fetched in a day, not the number of requests.
InMail
The number of InMails depends on the LinkedIn subscription: for example, Career subscriptions start with 5 InMails per month, while some Recruiter contracts include thousands of shared InMails. Check the available credits with Get InMail Credits.
Free InMails to Open Profiles: open profiles can be identified with the is_open_profile field of the profile retrieved from Recruiter or Sales Navigator (the result is specific to the given account). LinkedIn allows at most 800 free InMails per month per account, and reduces this number for some accounts depending on their type, history, acceptance rate, and the product used to send (Classic, Sales Navigator or Recruiter). You get the same result as in the LinkedIn UI. More information on Recruiter limits here.
In some cases, LinkedIn may still require available InMail credits, even for a free InMail to an Open Profile. If the account has no credit left, the send may fail depending on the product and LinkedIn-side rules.
Space InMails randomly and keep to 30–50 per day to make the most of the monthly allocation.
Detecting accepted invitations
Polling relations or the invitation list every hour, or at fixed times such as 8:00 AM daily, is easily flagged as automation. When you perform an initial sync in your tool, you can call these endpoints several times; after that, retrieve only the first page a few times a day, at random intervals of several hours. See Detecting Accepted Invitations for the recommended approaches.
Chats and messages
Unipile synchronizes the messaging inbox on its side, so you can fetch chats, messages and participants without these limitations.
Other actions
For any action not listed above, minimize usage, space calls at random intervals, and by default keep each action under 100 per day per account (e.g. retrieving company profiles or posts, sending messages to connections, commenting, or adding reactions).
LinkedIn Recruiter sessions
LinkedIn Recruiter limits the number of simultaneous sessions. Logging into Unipile with LinkedIn credentials may trigger a warning from LinkedIn, reminding users not to share account credentials. Users must acknowledge this message. If LinkedIn detects a new session afterward, it displays the current sessions and prompts the user to choose which session to end to keep using LinkedIn in their browser.
While this does not pose a long-term risk to the user's account, it creates a poor user experience, as the user needs to reconnect their account to Unipile each time this popup appears.
To avoid this limitation, don't activate the Recruiter product if your application doesn't need it (see the product selection options in Link LinkedIn accounts).
If Recruiter is required, users should connect their account using cookies: include cookies in the allow_methods field of the LinkedIn configuration (see Link LinkedIn accounts). Retrieving cookies requires users to open their browser's developer tools, so this process needs to be clearly explained to non-technical users. The best way to handle this is a Chrome extension that users install, which collects the necessary cookies in the background.
WhatsApp
| Rule | Recommendation |
|---|---|
| Account to connect | A real account with historical activity, never a brand new account dedicated to software |
| Fresh accounts | Can be blocked after only 2–3 new chats: warm them up over several days with a few real conversations before any outreach |
| After connecting or reconnecting | Wait up to 24 hours before creating new chats or starting outreach |
| Delay between messages | At least 10–20 seconds |
| New chats (outreach) | Keep the number low and prioritize contacts likely to reply |
| Spam signals | Too many new chats without replies, or many spam/block reports, can temporarily restrict the account |
Connect accounts with old activity: WhatsApp is much more tolerant with accounts that have a real usage history. Accounts created only to be used by software are quickly suspended.
Wait after connecting or reconnecting an account: WhatsApp may detect an account that opens a new session and immediately starts outreach as suspicious behavior. This applies after connecting, reconnecting, or disconnecting/reconnecting an account.
Engage users in discussion: Design messages to initiate interaction and encourage replies. The first message should prompt a response to maintain active conversations.
Respect delays between messages: Realistic delays mimic human behavior and align with natural conversation patterns.
Limit new chat creations: The number of new chats is a metric monitored by WhatsApp. If you initiate too many new chats without receiving responses, or if there are many spam/block signals, WhatsApp may temporarily restrict the account. Avoid aggressive outbound campaigns.
Instagram
| Action | Recommended maximum per account |
|---|---|
| Any action (following, outreach, likes, comments…) | 100 per day and 10 per hour |
| Replies to inbound messages | No limit: you can reply to all of them, like in the UI |
For new or inactive accounts, begin with lower activity levels and gradually increase them over time.
To better emulate human behavior, space out all actions randomly instead of executing them at regular intervals. Distribute these actions across multiple time slots during working hours for a more natural pattern.
Instagram may display a warning message such as: "We suspect automated behavior on your account." You can ignore this message and continue using automation: we have not observed additional account restrictions or negative consequences for users who received this warning and kept using our API as usual.
Facebook
| Action | Recommendation per account |
|---|---|
| All requests | 10 to 50 per day |
| Friend requests | Up to 50 per day, only to people with more than 10 mutual connections |
| Direct messages (DMs) | Start at 15 per day, add 5 each week, up to 50 per day |
| Login attempts | Never retry a failed login automatically: wait for the user to act |
Facebook doesn't set an official limit on friend requests or direct messages, but going over 50 per day puts the account at risk. Sending friend requests only to people with mutual connections helps keep the account secure, and increasing DMs gradually lets the account build a normal activity history.
Avoid repeated login attempts: Rapid repeated logins can lead Facebook to lock the account. If a login fails, don't retry automatically: wait for the user to act.
Email deliverability
In most cases, major email providers like Google, Microsoft, and IMAP providers automatically configure DKIM, SPF and eventually DMARC when users set up their internal email systems. If you're simply creating a system for email sync and manual sending from your app, you can bypass managing these settings. Just instruct users to connect their email, ensuring they experience the same delivery results as with Outlook or Gmail.
However, if your system involves outreach or automatic sending at higher volumes, it's advisable to verify the proper configuration of these parameters to ensure optimal deliverability at scale.
If your company domain sends more than 5,000 emails daily to Google or Yahoo, you need to maintain an abuse complaint rate of 0.3% or lower, or all company emails will be blocked by Google. All traffic for your domain is included in this limit: newsletters, notifications, internal emails, etc.
Gmail
| Emails sent per account | Gmail | Google Workspace |
|---|---|---|
| Official limit | 500 per day | 2,000 per day |
| Recommended | 50–100 per day | 100–150 per day |
| Recommended, with good sending quality | Up to 150 per day | Up to 300 per day |
| New accounts | Start at 20–50 per day | Start at 20–50 per day |
Recommended sending limits: Staying well below the official limits avoids being flagged or blocked. Increase volumes only if sending quality is good (replies, low bounce rate), and increase gradually for new accounts.
API calls limits: Gmail limits the number of calls you can make, with a quota shared between all actions. Spread your calls over time to avoid hitting these limits (429): Gmail API usage limits.
Way to increase the limit: You can create multiple domains in your Google Workspace and link them as aliases to your main email. With our API, you can list aliases and use them as the 'from' address. This lets you distribute your reputation across different domains with only one connected Gmail account. Learn more.
Outlook
| Microsoft 365 subscribers | Limit |
|---|---|
| Daily recipients | 5,000 |
| Maximum recipients per message | 500 |
| Daily non-relationship recipients | 1,000 |
Limits may vary based on usage history and will be lower for non-subscribers. A "non-relationship recipient" is someone you've never sent email to before. The sending limits of any third-party connected accounts depend on the service provider.
Apart from these official limits, we advise respecting the recommended sending limits of the Gmail section.
IMAP
The limitations may vary depending on your email provider. Please refer to your users' provider documentation or ask them directly for specific details.
Apart from official recommendations, we advise respecting the recommended sending limits of the Gmail section.
Pagination
Be aware that paginated methods have their own provider-related limitations, documented in API Usage.
Updated 3 days ago