ApivomApivom
Get Demo

LinkedIn Marketing Solutions API Connector

LinkedIn's versioned Marketing Solutions API — Community Management (organization posts, image and document uploads, page admins, share statistics, follower counts), Campaign Manager (ad accounts, campaigns, creatives, audience insights, conversions, reporting, lead-gen forms) — 238 routes in Apivom Atlas; Apivom Mars publishes your company page posts with it.

What you can do

  • Community Management: organization posts (text, multi-image, document), image/document upload initialisation, page admin ACLs, lifetime and time-bound share statistics, follower counts — the routes Apivom Mars uses to publish and measure company page posts
  • Audience Insights: targeting facets (seniorities, job functions, titles, skills, industries, company size and growth, geo typeahead) and audience composition queries
  • Campaign management: ad accounts, campaign groups, campaigns, creatives, budgets and bids
  • Measurement: analytics and reporting, conversion tracking, lead-gen form responses
  • Versioned API with the LinkedIn-Version header; 238 routes, 155 read-only

Use cases

  • Company page posts from your content calendar — Mars drafts the post, renders the carousel slides and publishes them to the connected company page, then records the post URN so share statistics flow back into the campaign report.
  • Size an audience before you spend — Query targeting facets and audience composition to estimate reach for a segment — by seniority, function and company size — before creating the campaign.
  • Campaign reporting in your own warehouse — Pull analytics and conversion data for every campaign on a schedule and join it with CRM outcomes instead of exporting from Campaign Manager.
  • Lead-gen forms straight to the CRM — Fetch lead-gen form responses as they arrive and create leads with the campaign and creative that produced them.

LinkedIn Marketing Solutions is the versioned API behind both Campaign Manager and company page management, addressed with the LinkedIn-Version header. Apivom Atlas catalogues 238 of its routes. The Community Management family — organization posts, image and document upload initialisation, organization ACLs, share statistics and follower counts — is the part Apivom uses in production: Apivom Mars connects a company page once as a page admin (w_organization_social, r_organization_social, rw_organization_admin; 60-day token refreshed daily), publishes multi-image carousel posts by initialising each image upload and creating the post, and reads lifetime share statistics and follower counts into its channel metrics. Mars talks to api.linkedin.com directly with that token. The Audience Insights family enumerates every targeting facet and answers composition questions; the campaign family manages ad accounts, campaign groups, campaigns, creatives, budgets and bidding; the measurement family covers analytics reporting, conversion tracking and lead-gen form submissions. Those advertising routes have no Apivom product workflow today — they require a Marketing Developer Platform application — and are available to agencies and marketing teams building on them, scoped per customer. Atlas publishes the credential contract and the AI integration guide (llms.txt).

Authentication

A LinkedIn OAuth 2.0 access token — 3-legged for member-authorised actions or client-credentials for partner programs — sent as Bearer per request, with the LinkedIn-Version header on versioned APIs. Stored tokens are encrypted in your Iris tenant; Apivom Atlas forwards, logs and stores nothing.

Frequently asked questions

Which part of this API does Apivom use today?

The Community Management routes: Apivom Mars publishes organization posts (multi-image carousels) to a connected company page and reads share statistics and follower counts for its metrics. The Campaign Manager routes — ads, audience insights, conversions, lead-gen forms — are catalogued and documented but have no product workflow; wiring them into one is scoped per customer.

What does LinkedIn require to use this API?

A LinkedIn developer application approved for the Marketing Developer Platform, OAuth scopes such as r_ads, r_ads_reporting and rw_ads granted by an ad-account admin, and the LinkedIn-Version header on every versioned call. Apivom's connector forwards these; obtaining the approval is between you and LinkedIn.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.