Our platform offers APIs to connect with various providers, facilitating seamless integration for developers. However, it's crucial to understand and manage the limits and restrictions imposed by each provider to ensure smooth operation of your applications. Below are the limitations and guidelines for interacting with different providers:

These limits are conservative recommendations. You may increase the values at your own risk. Exceeding LinkedIn's limits will result in an HTTP 429 error. Ensure your system handles this error effectively to avoid warnings related to automation on your user account.

To emulate human behavior, space out actions randomly with intervals of approximately one minute, distributed across multiple launches during working hours.

For new or inactive accounts, start with low quantities and increase gradually. Accounts with fewer than ~150 connections or recently created accounts may experience delivery issues with invitations, which may require manual verification. Fake accounts are well-detected by LinkedIn, even without automation. We strongly recommend using only real accounts.

These limits are defined per LinkedIn account. They are independent of the route and do not accumulate.

Connection Requests (Invitations):

For a paid and active LinkedIn account, you can send between 80 and 100 invitations per day, and approximately 200 per week (with a message of up to 300 characters).
For a free account with some history, you can send around 15 invitations per week (with a 200-character message) or up to 150 invitations without adding a note.

If you hit the invitation limit, LinkedIn will return a specific error 422/cannot_resend_yet.

Retrieve a User Profile (Profile Visits/ID conversion):

~100 profiles per account per day

If account have Sales Navigator or Recruiter, you can perform an additional ~100 requests per account per day by switching "api" parameter in the profile retrieval request.

Search Results:

To retrieve a list of search results, we advise limiting your query to a maximum of 1,000 profiles per day (or 2,500 profiles for a Sales Navigator/Recruiter account).

LinkedIn limits the number of results displayed to 1,000, even if the total shows more. To retrieve all results, filter your query using parameters and perform multiple searches (2500 for People and 1500 for Companies on Sales Nav).

Chats Retrieving:

We manage messaging inbox synchronization on the server side, ensuring seamless synchronization of chat lists and messages. This enables users to access and fetch their data without limitations via routes such as Messages, Chats, and Attendees.

Other Routes:

For all other unlisted routes, follow the same principles:

Minimize usage as much as possible.
Space out calls at random intervals.
By default, limit each action to 100 per day per account (e.g., retrieving company profiles, retrieving posts, sending messages to connections, commenting, or adding reactions..).

LinkedIn Recruiter

LinkedIn Recruiter has specific limitations on the number of simultaneous sessions. Logging into Unipile using your 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, LinkedIn will display a message listing the current sessions and prompt the user to choose which session to end to continue 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 will need to reconnect their account to Unipile each time this popup appears.

To avoid this limitation, you can disable the Recruiter feature if it is not specifically needed in your application. This can be done by using the disable_feature parameter in the hosted authentication route.

If the Recruiter feature is required, users must connect their account using cookies. This option is available on the login page but requires users to open their browser's developer tools to retrieve the cookies. For non-technical users, this process needs to be clearly explained.

The best way to handle this is by creating a Chrome extension. This extension would simply ask users to install it, allowing you to collect the necessary cookies in the background. We can provide a basic skeleton for an extension to collect cookies with the appropriate permissions, but you will need to implement additional logic in your backend. You can find more details here.

Connect Accounts with Old Activity: Avoid using brand new accounts exclusively for software purposes. Instead, utilize WhatsApp accounts with historical activity from real users to prevent account to be suspended. If you use fresh account they can be blocked after 2-3 new chat, they need to be warmup during days with one or two chats.

Engage Users in Discussion: Design messages to initiate interaction and encourage replies. The first message should prompt a response to maintain active conversations.

Respect Delay Between Messages: Incorporate realistic delays between messages to mimic human behavior. Avoid sending messages with intervals shorter than 10-20 seconds to align with natural conversation patterns.

Number of new chat creations (outreach): This is a metric monitored by WhatsApp. If you initiate too many new chats without receiving responses or if there are a high number of signals of spam/block, it may temporarily restrict your account.

By adhering to these guidelines, developers can optimize their software's WhatsApp integration and potentially send several hundred messages per day per WhatsApp account without violating policies.

Instagram

Account Requirement: Only connect old accounts with months of history to our APIs. Freshly created accounts will be blocked.

Facebook

Maximum sending between 10 and 50 requests per day is recommended. It's essential to exclusively send requests to individuals with more than 10 mutual connections to uphold account security. While there is no set limit on friend requests or direct messages (DMs) sent, it's advised not to surpass 50 per day. Following the training guidelines, it's best to start with 15 DMs daily and incrementally increase by 5 each week until reaching the maximum of 50 DMs per day.

Gmail

Differences Between Gmail Accounts and Google Workspace: Gmail accounts can send up to 500 emails per day, while Google Workspace accounts can send up to 2000 per day officially.

Recommended Sending Limits: To avoid being flagged or blocked, limit Gmail sending to 50 to 100 emails per day and Workspace sending to 100 to 150. Depending on sending quality, replies, and bounce rate, these limits may be increased up to 150 for Gmail and 300 for Workspace. For new accounts, start with 20 to 50 emails per day and gradually increase.

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 will allow you to distribute your reputation across different domains with only one connected Gmail account. https://support.google.com/a/answer/7502379?hl=en

Outlook

The limits for Microsoft 365 subscribers are:

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 upon the service provider.

Apart from official recommendations, we advise respecting the "Recommended Sending Limits" in Gmail part.

Email IMAP

The limitations may vary depending on your email provider. Please refer to your users provider's documentation or inquire with them directly for specific details.

Apart from official recommendations, we advise respecting the "Recommended Sending Limits" in Gmail part