LinkedIn’s Marketing API requires manual review for every application, unlike Google Ads (automatic approval at basic access level) or Meta (automatic approval for standard permissions). Rejection requires creating a new application from scratch — there is no resubmit or appeal process.
The Setup Steps
The process starts like every other platform: create a Developer Portal app, associate it with a LinkedIn Company Page, and configure your OAuth credentials. You’ll need to be a super admin on the Company Page, or get super admin verification from someone who is. LinkedIn gives you a 30-day window to complete that verification step — miss it and you have to restart.
Once the app is created, you navigate to the Products tab and apply for “Advertising API” access. This is where LinkedIn diverges from every other platform. Instead of reviewing your app against a checklist and granting access automatically, a human at LinkedIn reads your application and makes a judgment call.
The Manual Review
The manual review can take weeks to months. There’s no guaranteed timeline, no way to expedite it, and no programmatic way to check status. You submit and wait.
Common rejection reasons:
- Missing or incomplete company information on the Developer Portal app
- Unsupported use case (LinkedIn is cautious about anything that resembles competitive intelligence or ad management beyond your own accounts)
- Insufficient detail about how you’ll use the data
- The Company Page association looks thin or suspicious
If you’re rejected, you can’t reapply with the same developer application. You need to create a new app entirely and submit a fresh application. There’s no appeal process, no “update this and resubmit.” The slate is wiped. This makes getting the application right the first time consequential.
Writing an Application That Gets Approved
LinkedIn is looking for signals that you’re a legitimate business building internal analytics tools, not scraping competitor data or building an unauthorized ad management layer. The application asks you to describe how you’ll use the data — take this seriously.
What helps:
Include detailed screenshots of your internal analytics interface, even if it’s a rough prototype. Showing LinkedIn that there’s an actual tool being built (not just a data dump) increases the legitimacy signal.
Explain explicitly that the use case is reporting and analytics, not ad management. LinkedIn is more cautious about applications that want to create or modify ads programmatically. Pure analytics use cases (read-only access to campaign performance data) are easier to get approved.
Reference your company’s LinkedIn Page prominently. The connection between the developer app and a real, active LinkedIn company presence matters. If the Company Page has recent posts, a full profile, and actual followers, that’s better than an empty page created yesterday.
If you’re a consultancy applying on behalf of a client, include the client’s company details in the application, not just your own. LinkedIn is looking for the ultimate business rationale, and “I’m building this for Client X who runs campaigns for their B2B SaaS product” is more convincing than “I’m a consultant.”
Some teams have found that mentioning an established integration partner relationship helps. If you’re building on top of a platform that LinkedIn recognizes as a legitimate ecosystem player, that association can help.
Additional Access Layers
The standard “Advertising API” access gets you the adAnalytics endpoint, campaign and creative management, and basic account data. Some capabilities require additional approvals on top:
Lead Sync API — required to access lead generation form submissions programmatically. Separate application, separate approval.
Private APIs — Matched Audiences (uploading audience segments), Audience Insights, and Media Planning tools. These require yet another layer of approval. Some of these never become available to direct developers at all; they’re gated to certified LinkedIn Marketing Partners.
Company Intelligence API — launched November 2024, provides company-level engagement data linking paid impressions to CRM pipeline. Not available via direct API access at all — only accessible through certified partners (Channel99, Dreamdata, Factors.ai, Fibbler, Octane11). If you need company-level attribution, you’re routing through a third party regardless of your API approval status.
Timeline Expectations
Budget weeks to months for the initial Advertising API approval. Budget additional weeks for each subsequent access layer you need. If your pipeline requires lead form data, plan for the Lead Sync API approval in parallel with (not after) your main API application.
For teams under time pressure, this is the strongest argument for using a managed extraction tool like Fivetran. Fivetran already has an approved LinkedIn partner relationship, so their connector doesn’t go through the standard manual review. You still need to connect your LinkedIn ad account to Fivetran via OAuth, but that’s a self-service flow, not a weeks-long review process. If you can’t afford to wait on API access, managed tools route around the bottleneck entirely.
After Approval
Once approved, token management becomes the ongoing operational concern. LinkedIn’s OAuth tokens are short-lived. See LinkedIn Ads OAuth Token Management for the re-authentication model.
The LinkedIn Ads Analytics Endpoint has its own constraints: no pagination, a 15,000-element cap, 20 metrics per request.