LinkedIn Advertising API Technical Sign Off: The 23-Capability Demo Between You and Partner Access
Most teams treat LinkedIn API access as a form submission. Get approved for the Advertising API, build the integration, ship it. What the Marketing Developer Platform documentation actually describes is a longer road — one that ends in a scheduled live demo where a LinkedIn reviewer walks through a published list of capabilities your product is expected to already have built.
The gate that is not on the application form
LinkedIn’s own integration requirements page states that LinkedIn is “in the process of rolling out a Technical Sign Off process for the Advertising API program”, and explains why: to ensure “there are no gaps in integrations and that partner products keep up with the latest features and updates released by LinkedIn.”
Read that as a product requirement, not a paperwork requirement. The documentation asks partners to “plan and incorporate these features early in your design” — which is a polite way of saying that discovering the list after your architecture is frozen is expensive.
A demo will be scheduled during which you will be asked to showcase all your product capabilities. LinkedIn can suggest modifications which should be completed for the sign off. If all criteria are met, the technical sign-off is awarded.
Three separate things people call “LinkedIn API access”
Product access
Which API product you are approved for. LinkedIn documents Advertising, Community Management, Events Management, Lead Sync and Conversions as open to approved developers, while Matched Audiences, Audience Insights and Media Planning are restricted to developers meeting additional criteria. Company Intelligence is not currently accepting new applications.
Access tier
Advertising and Community Management each have a Development and a Standard tier. All applications start at Development. On Advertising, Development gives unlimited read but edit rights on only five ad accounts and a single test account creatable through the API.
Technical sign off
The partner-facing review. Not a form — a demo against a published rule set covering OAuth handling, account hierarchy, campaign creation, targeting parity and reporting. This is the layer almost nobody plans for.
What the published rules actually ask you to demonstrate
The requirements are grouped and numbered, and the grouping tells you where LinkedIn expects the weak spots to be.
| Group | Rules | What is really being tested |
|---|---|---|
| Basics | ADS-001 to ADS-006 | Six of the twenty-three rules are entirely about token lifecycle: OAuth 2.0 with the right scopes and consent screen, a periodic validity heartbeat, detecting access token expiry, re-triggering the flow, minting new tokens from refresh tokens, and detecting refresh token expiry too. Most integrations implement roughly half of this. |
| Account structure | ADS-101 to ADS-107 | Retrieving accounts, campaign groups, campaigns and creatives with status, visualising the hierarchy, and pausing, activating and rebidding from your own UI. Read-only dashboards fail here. |
| Campaign creation | ADS-201 to ADS-206 | Objective Based Advertising in your creation UX, two or more campaign types, edit and archive, creatives from an existing share and from a dark share, plus start and end scheduling. |
| Targeting | ADS-301, ADS-302 | Parity with the Campaign Manager UI on all targeting facets, and a UI that expresses boolean include and exclude structure. This is the single most under-built area. |
| Reporting | ADS-501, ADS-502 | Reporting by campaign hierarchy and by demographic pivots — the latter interacting with LinkedIn’s privacy approximation rules, which add noise and enforce a minimum threshold on reported metrics. |
Why this becomes a project, not a checkbox
The tier you start on shapes what you can even test
Development tier caps edit access at five ad accounts and allows exactly one API-created test account. Anything resembling multi-account campaign management has to be designed against a ceiling you have not been granted yet.
Standard tier is requested separately, through support
LinkedIn documents the Standard Advertising API tier as requested via a support ticket on the Developer Support Portal — a different motion from the product application, with a different evidence burden. Community Management runs on its own clock entirely.
The demo is scheduled through a business contact, not a queue
The sign off is initiated by contacting a LinkedIn Business Development point of contact when you are nearing completion. There is no self-serve button, which means readiness has to be judged before you ask.
Reviewers can require modifications before signing off
LinkedIn states it may suggest modifications that must be completed for sign off. Each round is engineering work against a live roadmap, so the cost of arriving under-built compounds.
Meeting the minimum is explicitly not enough on its own
The documentation is direct about it: LinkedIn “reserves the right to review applications and select partners at its discretion and a partner might not be upgraded even if they meet these minimum requirements.” Positioning and use case matter alongside the build.
What a well-prepared submission looks like
The right product and tier requested for the actual use case, instead of a broad ask that invites questions the team cannot answer yet.
Token lifecycle, hierarchy control, creation flows, targeting parity and reporting designed against the published capability list from day one.
A walkthrough that maps cleanly onto how the reviewer will assess it, rather than a product tour that leaves gaps visible.
Data handling, scope usage and compliance with the Marketing API Program Terms stated consistently across the app, the product and the privacy policy.
Where these applications go wrong
- Treating the twelve-month clock as advisory. On Community Management, LinkedIn states that if you do not apply for Standard tier within twelve months of receiving access, it will remove your API access due to inactivity.
- Building a read-only dashboard and applying as a campaign management partner. Seven of the rules require write control over the hierarchy from inside your own product.
- Half-implementing token handling. Detecting access token expiry is common. Detecting refresh token expiry and re-triggering the flow cleanly is not, and it is its own numbered rule.
- Shipping partial targeting. Parity with every Campaign Manager facet, plus a boolean include and exclude structure, is a substantial UI project on its own.
- Requesting closed permissions. Several scopes are documented as closed or restricted, and asking for them signals the use case was never mapped to the published product catalogue.
- Assuming two-legged OAuth is available. LinkedIn states all Marketing API Program permissions are three-legged; server-to-server designs that skip member consent do not fit the program.
- Applying to a restricted product without the prerequisite. Advertising API access is documented as a mandatory prerequisite for Matched Audiences, Audience Insights and Media Planning.
The decision worth making before you build
The LinkedIn Marketing Developer Platform rewards teams who read the requirements as a product specification and design backwards from them. It punishes teams who treat access as an administrative step and discover the capability list at demo time, when the architecture is already carrying customers.
Mapping a use case to the right product and tier, aligning the build with the published requirements, and preparing the application and demo narrative around what LinkedIn evaluates is the work we do. See the services overview, plus the related breakdowns on the Advertising API Standard tier upgrade, Community Management API access, and Sign In with LinkedIn (OpenID Connect) setup.
Independent consultancy. Not affiliated with, endorsed by, or a partner of LinkedIn Corporation or Microsoft. Platform requirements change; every claim above is drawn from LinkedIn’s published Marketing Developer Platform documentation at the time of writing and should be re-checked against the current docs before you build. Access and partner decisions rest solely with LinkedIn, and no specific outcome can be guaranteed.