How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

LinkedIn Conversion Events Streaming Workflow API

1. Obtain user authorization with consent to create and manage conversions using `rw_conversions`, `r_ads` permissions in the scope.2. Retrieve authenticated user's sponsored Ad Accounts where user has a non-viewer user role.3. Ask the user to select one of their Ad Account where conversion events would be streamed.4. Fetch existing Conversion Rules for CAPI in the selected Ad Account5. Allow the user to choose if they want to create a new Conversion Rule or update an existing one6. Create a new Conversion Rule (skip this step if the user chose to update an existing Conversion Rule)7. Fetch active campaign URNs to associate with conversion rule8. Associate campaigns to conversion rule for campaign attribution and optimization9. Stream conversion event to the conversion rule 10. Stream multiple conversion events to the conversion rule

LinkedIn Conversion Events Streaming Workflow API is one of 65 APIs that LinkedIn publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Conversion Events Streaming Workflow. 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 6 operations across 5 paths, and defines 9 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.

6 operations 5 paths 9 schemas 3 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.linkedin.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

LinkedIn Conversion Events Streaming Workflow 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 6

Across 5 paths, the API surfaces 6 operations — 3 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Conversion Events Streaming Workflow 6

1. Obtain user authorization with consent to create and manage conversions using rwconversions, rads permissions in the scope. 2. Retrieve authenticated user's sponsored Ad Accoun…

GET
/adAccountUsers
LinkedIn 2. Retrieve Authenticated User's Sponsored Ad Accounts
getRetrieveAuthenticatedUsersSponsored 4 params → 200
GET
/conversions
LinkedIn 4. Fetch Existing Conversion Rules for CAPI in the Selected Ad Account
getFetchExistingConversionRules 5 params → 200
POST
/conversions
LinkedIn 6. Create a New Conversion Rule
postCreateANewConversion 2 params body → 201
GET
/adAccounts/{sponsoredaccount_id}/adCampaigns
LinkedIn 7. Fetch Active Campaigns
getFetchActiveCampaigns 6 params → 200
PUT
/campaignConversions/(campaign:urn:li:sponsoredCampaign:{campaign_id},conversion:urn:lla:llaPartnerConversion:{conversion_id})
LinkedIn 8. Associate Campaigns to Conversion Rule
putAssociateCampaignsToConversion 4 params body → 204
POST
/conversionEvents
LinkedIn 10. Stream Multiple Conversion Events to the Conversion Rule
postStreamMultipleConversionEvents 3 params body → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are CreateANewConversionResponse201 (14 properties), FetchActiveCampaignsResponse200 (2 properties), RetrieveAuthenticatedUsersSponsoredResponse200 (2 properties), FetchExistingConversionRulesResponse200 (2 properties). Each schema is shown below with its type and property counts.

AssociateCampaignsToConversionResponse204
string
CreateANewConversionRequest
object
RetrieveAuthenticatedUsersSponsoredResponse200
object
2 properties
StreamMultipleConversionEventsResponse200
object
1 property
CreateANewConversionResponse201
object
14 properties
AssociateCampaignsToConversionRequest
object
StreamMultipleConversionEventsRequest
object
FetchActiveCampaignsResponse200
object
2 properties
FetchExistingConversionRulesResponse200
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

linkedin-conversion-events-streaming-workflow-api-openapi.yml Raw ↑

Other APIs LinkedIn publishes across the network.

LinkedIn Consumer API
LinkedIn Access Control API
LinkedIn Account Management API
LinkedIn Ad Accounts API
LinkedIn Ad Targeting Entities API
LinkedIn Advertiser Transparency API
LinkedIn Application Retrieval API
LinkedIn Application Synchronization API
LinkedIn Application Updates API
LinkedIn Apply Connect Jobs API
LinkedIn Audience Counts API
LinkedIn Audience Insights API
Where this information came from

This is an independent, third-party profile of LinkedIn Conversion Events Streaming Workflow 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.