bannerColor WARNING_YELLOW templateName stackForums

LinkedIn Platform Guidelines

LinkedIn Platform Guidelines

The LinkedIn APIs are designed to allow users to use their LinkedIn account in your applications. Following these guidelines ensures that our common users have a great experience on your site and come back for more. If your application is found to be in violation of these guidelines, LinkedIn may limit or block your access to the site and the APIs.

We have a Partner Program, for selected developers. Learn more about this program, including the application process, at

  1. High Level Guidelines

    These are the summary rules that cover the major themes. Most of the details roll up to one of these key rules. Please refer to our API Terms of Use for additional detail.

    1. No LinkedIn data can be stored: The only exceptions are storing the Member ID for subsequent API calls, and storing the user's profile data when given explicit user permission by the owner of the profile using a LinkedIn-provided interface to obtain the user's consent.
    2. Don't share your Access Codes/API Keys with anyone.
    3. Data from one user's LinkedIn account/network may not be exposed to another user: People's views of their networks are private to them, based on the connections they have. Each user must grant your application access to their LinkedIn network and they can only see data from their own LinkedIn network. For example, you cannot gather information about a LinkedIn member in one user's LinkedIn network and show that information to other users.
    4. You cannot use the APIs in conjunction with, or combine any Content from the APIs with data scraped by you or other third parties from LinkedIn. While LinkedIn encourages the use of its developer resources to create innovative applications, the LinkedIn APIs should be the sole source of LinkedIn member data. Using LinkedIn member data scraped from third parties, including but not limited to Search APIs, or improperly obtained by yourself or others in your application (or otherwise) is not permitted.
    5. You must show the agreement screen in its own window: The user agreement page where the user grants access to their LinkedIn account must be presented in a browser window where the URL is visible. That should be the same browser window/tab, but can also be in a popup window. It cannot be iframed into the current page, though. The user must be able to verify that the URL is
    6. You cannot provide API access to your customers: You cannot provide use of the LinkedIn APIs as a feature of your product. This applies mainly to platforms that want to wrap the LinkedIn APIs. LinkedIn must have a direct relationship with any application making API calls.
  2. 2. Polite Use

    If everyone uses the APIs efficiently, there will be plenty to go around.

    1. If you have a lot of calls to make in a batch, submit them over a period of time. If you can space out your API calls as much as possible without impacting user experience, this will result in the best API performance for you and all other developers.
    2. Ask for only the minimum data fields your application needs to work properly. Many calls let you ask for individual fields and collections. Asking only for the data fields necessary for your Application to function will give you the fastest performance times and least data to parse.
    3. Do not circumvent LinkedIn's rate limits. For example, do not spread your API calls for a single application across multiple keys to bypass our rate limit restrictions. For example, do not ask or expect your customers to supply their own developer / API key as a method of circumventing rate limits. If you bump up against our rate limits, please contact us so we can work with you to find the best way to accommodate both your and our objectives under this program.
    4. LinkedIn exists to help professionals leverage the value of their professional reputations and relationships. Do not implement features or business practices that are harmful to the professional reputation, relationships or professional ecosystem of LinkedIn members.
  3. 3. Data Storage

    LinkedIn users own their data. They need to have control over it. They might want to change it, change the visibility rules, or even delete it. If the data is stored in third party databases, they lose control over it. So, you cannot store the data we return in an API call.

    1. You cannot store any data you receive from the LinkedIn APIs except for the member IDs you receive.
    2. If you specifically ask the profile owner to store his/her profile and make it clear that you will be storing it, then you may store the profile of the user who granted you access. The details of this are provided in Section 3.4 of the API Terms. You may only store the profile of that person, not the profile data of that person's connections, network updates, or other network information.
    3. You may not transfer LinkedIn data to anyone beyond displaying it to the user engaged with your application.
    4. You may not use Content obtained through the Apply with LinkedIn Plugin for the purpose of creating profiles on your own or a third party site/service or application templates for use across multiple job applications.
  4. 4. Advertising and Promotions

    We are providing APIs so you can build great integrated features for your users, not so you can directly monetize or build your business on that data.

    1. You cannot use LinkedIn data to determine whether to display ads or promotions, or which ads or promotions to display.
    2. You cannot use LinkedIn data to determine the content of ads or promotions.
    3. You cannot use LinkedIn data within an ad.
    4. When displaying content from LinkedIn, you cannot insert ads or promotions within that content.
    5. Users should not be confused about whether content came from LinkedIn or your Application. So, for example, you cannot place ads within your display of a LinkedIn profile, network update, or message.
  5. 5. Revenue and Charging

    You may not charge our users for access to LinkedIn or data imported from it using the API.

  6. 6. Attributing content to LinkedIn

    We want to make sure that users understand where content is coming from. It can be disconcerting to see someone's profile or your own profile and not know where it came from.

    For all the details on how to use our branding elements, see Brand Mark Use below and the Branding Guidelines.

    1. When you display a profile, network update(s), connections, job, company, groups, or any other LinkedIn information, in whole or in part, you must make it clear that the information came from LinkedIn.
    2. Any time you display content from LinkedIn, you must include a link to see the content on LinkedIn. API calls include the links you need to send users to the right places.
    3. Use the IN icon or the LinkedIn name in text to attribute the information to LinkedIn.
    4. Place the attribution in the upper left corner or near any user interface elements such as buttons or links to other resources.
    5. When displaying company or job information, display a link or button giving the viewer an option to follow the referenced company on LinkedIn.
    6. When displaying groups content, accurately represent the post creator and participants in the conversation, and present the viewer with options to create a post or comment, like a post, or follow a post, or point the user back to the site.
  7. 7. Sending Messages, Sending Invitations, Updating Statuses, Posting Network Updates

    These features represent ways the user can message others. The "message" referred to below is the message, invitation, status update, or network update sent.

    1. Messages are a mechanism for your users to communicate about themselves to their connections. They should not be used to promote your product or service.
    2. A message must be triggered by a specific user action, not sent as an automated or scheduled event. A user simply navigating through your application is not a specific event.
    3. The user must be given a choice about whether to send the message. The user must opt into the messages being sent rather than opt out.
    4. For all messages but network updates, the user must be presented with the exact body and subject of the message and have the opportunity to customize both the subject and the body. Pre-prepared messages are allowed only if the user has full control over what is ultimately posted on their behalf.
    5. Message text you present by default must not contain superfluous characters for the purpose of becoming more noticeable than other messages. Message text must not be in all capital letters. For example, you may not propose to a user that they send a message such as **** HOW ARE YOU?!?!
    6. Message text you present by default must not contain profanity.
    7. If you include a URL in your message, it must not point directly to an executable or installer file of any type.
    8. The option to cancel without sending a message must have a presentation equal to the option to send the message.
    9. A message must come at or around the time the user took action to send the message.
    10. You must not offer any direct incentive as a reward for sending a message.
    11. You cannot use invitations as general messages. Invitations should be used only for the purpose of requesting an invitation to join the user's LinkedIn network. You may not use invitations to send messages that contain proposals, requests, offers, recommendations, or other non-invitation text.
    12. For messaging between connections, each message can be sent to up to 10 connections. Messages cannot be resent with the purpose of reaching more than 10 connections with the same message.

    Additional information for Posting Network Updates:

    1. Network updates should communicate significant professional activities by the user and as such often should only be initiated when users generate content on your site. For example, simply registering with your site or application is not a significant activity, and should not generate a network update.
    2. You cannot send a network update for visits to your site or registrations on your site.
    3. You cannot send a network update to suggest or require users visit or register on your site. Updates are to communicate the activities of your users that their connections will gain from knowing.
    4. Network updates associated with a user action must only be posted once.
  8. 8. Getting and Displaying Network Updates

    1. Network updates are private to the user for which they are intended. You may not request network updates for one person that you show to another person.
    2. You cannot modify the content of a network update or do anything that would misrepresent the original content and intent of the update.
    3. When displaying network updates, you must include the name of the person who made the update, the complete text of the update, and all links included in the update. Optionally, you should also include the picture of person who made the update.
    4. When displaying network updates, you must include all standard LinkedIn actions with that update, including the ability to like, comment, and send a private message to the poster of that update. These abilities are all provided via the LinkedIn API.
    5. When displaying a share update with rich content, you must display the image, source, title, and summary data provided, in addition to the text of the update.
    6. Where LinkedIn members are mentioned in the update, those user names must have a link back to the user's LinkedIn profile. That profile can be displayed on your side via an API call or can be a link to the LinkedIn website. API calls return the links you need.
    7. If you allow commenting on network updates, you must post those comments back to LinkedIn using the API.
    8. If you display a group of updates ("stream" or "feed"), you can add advertising or other promotional messages within that group of updates only if you clearly mark the advertisement or promotional content as such. Users should not mistakenly think your content is coming from their LinkedIn network updates.
    9. You may not include advertising within the content of a network update. You must always keep the name, update, picture, and links together without intervening content.
  9. 9. Press and Public Mentions

    Because LinkedIn does not systematically review and approve your use of our APIs, you may not make statements that indicate that there is a relationship between our companies or products beyond what is factually true.

    1. You may not indicate that there is any business relationship or partnership of any kind between your company and LinkedIn.
    2. You may not indicate that your integration is endorsed by LinkedIn in any way. Simply using the APIs in the way they were intended to be used does not constitute an endorsement of your product by LinkedIn.
    3. You may not include the LinkedIn name or branding elements on your partner pages.
    4. You may describe your integration only in factual terms. Exaggerating the extent to which you have integrated creates confusion and questions about what is really happening.
    5. You may never indicate that your integration provides visibility or access to the entire LinkedIn member base or portions of it beyond the user's own network. Because no single user has complete visibility to all LinkedIn data through the APIs, in no cases do integrations provide users complete access to the LinkedIn membership, messaging to them, or intelligence about them. You may never indicate that your integration exposes all the information of any type.
    6. You may not indicate that your integration allows a user to circumvent LinkedIn website requirements for visibility or access. The API Agreement prevents you from building such integrations and you should not claim to have done so.

    Example statements

    Examples here indicate what you can and cannot say. They are mean to provide guidance as examples, not to necessarily be the specific text of what you can and cannot say. Of course, you may use this recommended text if you want.

    Your Integration You Can Say You Cannot Say

    Display a profile for names on your site

    "See the LinkedIn profile for names you see."

    "Full visibility to any LinkedIn profile."

    Display the network updates from your user's connections

    "See updates from your LinkedIn connections."

    "See every time people in LinkedIn update their profiles."

    Send messages of any kind

    "Send a message to your connections on LinkedIn."

    "Reach LinkedIn members with your message"

    Each of these examples of what you cannot say indicates that your user can reach or has visibility to more than just connections or the user's network. You must not exaggerate the extent to which the user can see, discover, or reach the LinkedIn member base.

  10. 10. Brand Mark Use

    Within integrations you build, you may need to indicate that the content you are displaying comes from LinkedIn. To do that, you will need to use LinkedIn branding elements on your page. These guidelines document exactly how to do that.

    LinkedIn Marks refers to any element of the LinkedIn brand, including the LinkedIn name, logo, and IN icon. Other versions of the LinkedIn brand representation should not be used.

    All permitted uses of the LinkedIn Marks must conform to the following guidelines:

    1. See the Platform Guidelines for details about LinkedIn branding requirements for your specific integration.
    2. Use the iconic "IN" graphic to indicate LinkedIn features where a short, graphical element is required. Do not use the full LinkedIn logo.
    3. Use the name "LinkedIn" in text where you want to refer to the full name. Do not use the LinkedIn logo.