Getting Access to Matched Audiences API

Warning

Deprecation Notice: The Marketing Version 202510 (Marketing October 2025) will be sunset on October 15, 2026. We recommend that you migrate to the latest versioned APIs to avoid disruptions. For information on all the supported versions, refer to the migrations documentation. If you haven’t yet migrated and have questions, submit a request on the LinkedIn Developer Support Portal.

LinkedIn Matched Audiences API allows advertisers and partners to programmatically build, update, and manage custom audience segments to use as targeting selections in their advertising campaigns.

Supported Use Cases

  • Audience Upload: Upload a list of companies or contacts as a one-time transfer to build a custom audience segment.
  • Audience Streaming: Stream a set of companies or contacts to continuously sync and update an audience segment.
  • Retargeting: Build audiences of member accounts based on engagement with your website, ads, Lead Gen Forms, Company Page, LinkedIn Events, or Conversions API signals.
  • Predictive Audiences: Combine your first-party or third-party data with LinkedIn's predictive AI modeling to build a high-intent audience.

You have access to the following permissions:

  • DMP Segments: APIs to create and manage audience segments. Permission required is rw_dmp_segments.
  • DMP Segment Users: APIs to add or remove users from an audience segment. Permission required is rw_dmp_segments.
  • DMP Segment Companies: APIs to add or remove companies from an audience segment. Permission required is rw_dmp_segments.
  • DMP Segment Destinations: APIs to manage the destinations associated with an audience segment. Permission required is rw_dmp_segments.
  • Ad Segments: APIs to retrieve ad segment details. Permission required is rw_dmp_segments.

Applying for Matched Audiences API Access

Prerequisites

  • Read the LinkedIn Marketing API Terms and developer documentation.
  • You have one of the following use cases:
    • Reach specific target companies / accounts (ABM) by uploading company names or domains.
    • Reach specific known contacts by streaming user identities like user email, name.
    • Re-engage people who already interacted (e.g., CRM activity, website visits, or conversion/intent signals).
    • Exclude / suppress audiences (e.g., existing customers) to refine targeting.
    • Expand reach to similar audiences using lookalike or predictive modeling from a first-party seed.
  • Be prepared to share your business email address and your organization's legal name, registered address, website. Your business email address will have to be verified. If you don't receive the verification email, be sure to check your email's spam folder, junk folder, social tab, and promotional tab. Personal email addresses won't pass the review process.
  • Company Page Verification is required for a developer application applying for access to API. Ensure that you're not using a fake or test company page.
  • Ensure that a super admin of the LinkedIn Page associated with your organization has verified your developer application.
  • Ensure that your application doesn't include any portion of the LinkedIn or Microsoft names or logos (e.g. Linked or In).
  • Ensure that you have filled out all required fields in the access request form accurately and completely.

Important

Any failure to meet the above prerequisites will result in your access request being rejected.

Apply for Access

  1. Login to Developer Portal with your LinkedIn account.
  2. Choose your developer app from My Apps.

Note

If you or your organization doesn't have an existing developer app, create a new developer application.

  1. Navigate to the Products tab under your App name.
  2. From the list of Additional available products, search for the Matched Audiences product and select Request Access.
  3. Submit the form for LinkedIn to review your application.

Review Process

Once you have submitted the access request form, it will be reviewed by LinkedIn for the following:

  • Verified business email address.
  • Verified organization
  • Verified organization website and domain address
  • Application verified by LinkedIn Page associated with same organization.
  • Approved use case
  • Compliance with our terms, restrictions, and security, privacy, and trust requirements.

Next Steps

If your application is approved, you'll be notified over email about your access to the Matched Audiences API and your developer application will be provisioned with the required permission.

If your application is denied due to identity vetting failure, for example, when we were unable to verify that your organization is a legally registered active entity, you'll see an option to appeal for it from your developer portal application products, when you click on the Access denied link next to Matched Audiences API product. Please reach out via a Developer Support ticket.

If your application is rejected, for example, when your access request form provided insufficient details to approve your request, review the Prerequisites and Review Process to ensure your application is in compliance, and if you don't see any option to appeal for it, then you may create a new developer application, and submit a new access request form. Please see the Developer application review status definitions for details about each status and rejection message.

Please note that even if LinkedIn approves your integration, you're solely responsible for ensuring that your integration (including all use, disclosure, and storage of LinkedIn data) is, at all times, in compliance with: (a) the LinkedIn Marketing API Terms and the LinkedIn developer documentation; and (b) all other requirements or restrictions that LinkedIn separately communicates to you (e.g. during or after the review process). LinkedIn retains the right to monitor your application and suspend or discontinue access to the Matched Audiences API for any non-compliance with the LinkedIn Marketing API Terms, even if your application was previously approved by LinkedIn.

If you have additional questions or concerns, please reach out via a Developer Support ticket.