LinkedIn Use Cases > Sponsored API
In order to support collecting leads for sponsored use cases, a partner app needs to build a UX where a user is able to select the sponsored accounts and forms to collect leads for.###### Step 1: Obtain user authorization to access their leads###### Step 2: Get the user's sponsored accounts###### Step 3: Ask the user to select the sponsored account(s) whose leads they are interested in syncing###### Step 4: Validate the user's organization role tied to the chosen sponsored account###### Step 5: Retrieve forms for the user's selected sponsored account###### Step 6: Ask the user to select and map fields to the target destination (e.g. a CRM)###### Step 7: Allow the user to do a one time pull of all form responses looking back up to 365 days to grab any missed leads###### Step 8: \[PULL\] Schedule periodic form response pulls to collect leads###### Step 8: \[PUSH\] Allow the user to subscribe for lead notification webhooks###### Step 9: \[PUSH\] Fetch full lead data after a webhook notification is received
LinkedIn Use Cases > Sponsored API is one of 65 APIs that LinkedIn publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Use Cases > Sponsored. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, a changelog, release notes, and an API reference.
This API exposes 7 operations across 7 paths, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against a single base URL, https://api.linkedin.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
LinkedIn Use Cases > Sponsored API declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (OAuth2Auth) using the authorizationCode flow, exposing 1 scope.
By default, every request must be authenticated.
Paths & Operations 7
Across 7 paths, the API surfaces 7 operations — 1 DELETE, 5 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
In order to support collecting leads for sponsored use cases, a partner app needs to build a UX where a user is able to select the sponsored accounts and forms to collect leads fo…
Schemas 5
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are FetchFullLeadDataResponse200 (10 properties), GetTheUsersSponsoredResponse200 (2 properties), GetFormsForTheResponse200 (2 properties), ValidateTheUsersOrganizationResponse200 (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from LinkedIn 12
Other APIs LinkedIn publishes across the network.
This is an independent, third-party profile of LinkedIn Use Cases > Sponsored API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.