SocialMati
SocialOAuth 2.0 — Client ID + Client secretPricing verified 2026-10-06

LinkedIn

Publish to LinkedIn profiles and company pages, read comments and post statistics; base app for LinkedIn Ads.

AProvider definition

Provider
LinkedIn
What it does
Publish to LinkedIn profiles and company pages, read comments and post statistics.
Why we need it
Publish to LinkedIn profiles and company pages, read comments and post statistics; base app for LinkedIn Ads.
Used in
Social (publish, comments) · Performance ads (LinkedIn Ads)

BAccount requirements

Account type
LinkedIn developer application associated with your company Page
Prerequisites
  • LinkedIn Page admin rights
  • Legally registered organisation (for Community Management API)
Verification
Verify the app with the associated Page; Community Management API access requires a request and review.

CConnection method

Authentication
OAuth 2.0 — Client ID + Client secret
Where to enter it
  • Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
  • Per brand: App → Integrations → Connected accountsAnyone who manages the brand. Each brand connects its own accounts.

Setup steps

  1. 1linkedin.com/developers/apps → Create app; associate it with your company Page and verify it from the Page.
  2. 2Products: add “Sign In with LinkedIn using OpenID Connect” and “Share on LinkedIn” (personal posting).
  3. 3For company-page posting and comments, request the “Community Management API” product (separate review).
  4. 4Auth tab: add the Authorized redirect URLs shown below; copy the Client ID and Client secret.
  5. 5Enter them in the application. After Community Management approval, add the organisation scopes to the Scopes field.
  6. 6Connect accounts from Integrations → Connected accounts.

DPermissions & API scopes

Scope / permissionWhy it's neededRequested by
openidSign the user in (OpenID Connect).Default (personal profile)
profileRead the member's name and photo.Default (personal profile)
emailIdentify the connected member.Default (personal profile)
w_member_socialPublish posts as the member.Default (personal profile)
w_organization_socialPublish posts as a company Page (needs Community Management API).Company pages (after Community Management API approval)
r_organization_socialRead company Page posts and comments.Company pages (after Community Management API approval)
rw_organization_adminList the Pages the member administers and read Page statistics.Company pages (after Community Management API approval)
r_ads(LinkedIn Ads) Read ad accounts.LinkedIn Ads connection
r_ads_reporting(LinkedIn Ads) Read campaign results.LinkedIn Ads connection
rw_ads(LinkedIn Ads) Manage campaigns.LinkedIn Ads connection
r_organization_socialRead company Page posts and comments.LinkedIn Ads connection
w_organization_socialPublish posts as a company Page (needs Community Management API).LinkedIn Ads connection

This list is generated from the scopes the application's code requests.

EFree vs paid

Free account / free API access
Yes — no fee for API access once a product is granted.
Card or billing account required?
No.
Paid plan / costs
None for API access; advertising spend is billed by LinkedIn.
Quota and usage limits
Community Management API Development tier: 500 calls per app and 100 per member per 24 h; Standard tier after review raises limits.
Production restrictions
Company-page posting needs Community Management API approval, available only to legally registered organisations with a verified Page and business email. Development tier must be upgraded within 12 months.
Checked against official/current sources on 2026-10-06. Provider pricing changes often — re-check before publishing.

FSetup screenshots

Capture each step with real values masked. Save images as public/docs/integrations/linkedin/1.png … 10.png and they appear here automatically.

  1. Screenshot to add
    1. Account login / creation
    The provider's sign-in or sign-up page.
  2. Screenshot to add
    2. Developer console
    The developer console or dashboard home.
  3. Screenshot to add
    3. Project / app creation
    Creating the app or project used for this integration.
  4. Screenshot to add
    4. API enablement
    The API or product enabled for the project.
  5. Screenshot to add
    5. OAuth configuration
    Consent screen / OAuth settings with the redirect URIs.
  6. Screenshot to add
    6. API key / credentials creation
    Creating the key, secret or token (mask the value).
  7. Screenshot to add
    7. Permissions / scopes
    The scopes or permissions requested or approved.
  8. Screenshot to add
    8. Billing / quota settings
    Billing, credits or quota page.
  9. Screenshot to add
    9. Application connection
    The provider card in our application with fields filled (secrets masked).
  10. Screenshot to add
    10. Successful connection
    The green Test result or the connected account listed.

GApplication configuration

Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.

FieldRequiredExample / defaultNotes
Client IDYes—
Client secretYes••••••••Stored encrypted; shown masked after saving.
LinkedIn-Version header (YYYYMM)Optional202509
ScopesOptionalopenid profile email w_member_socialAdd w_organization_social r_organization_social rw_organization_admin once LinkedIn approves Community Management API access.

Paste these into the provider's console

Authorized redirect URL
https://api.socialmati.com/api/oauth/linkedin/callback
Authorized redirect URL (Ads — needs Advertising API access)
https://api.socialmati.com/api/oauth/ads/linkedin/callback

Connecting an ad account (LinkedIn Ads)

Covers Sponsored content in the LinkedIn feed. Connect with OAuth from Performance ads → Ad accounts, or paste a token:

  • • Access token (r_ads, rw_ads, r_ads_reporting) (required)
  • • Ad account ID (required)

HTesting

  1. 1Connect your LinkedIn profile and publish a test post.
  2. 2After Community Management approval, connect a company Page and publish to it.

ITroubleshooting

ProblemWhat to do
unauthorized_scope_errorThe scope isn't granted to the app — add the product or request access first, or remove the scope from the Scopes field.
Company pages not listedAdd rw_organization_admin (after approval) and make sure the member is a Page admin.
Posts fail after ~60 daysAccess tokens expire; reconnect the account.
Invalid credentialsCheck the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure.
Missing permissionsReconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved).
OAuth failureSign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app.
Redirect URI mismatchCopy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings.
API not enabledEnable the API/product for the project or app in the provider console and wait a few minutes.
Quota exceededWait for the quota window to reset (see section E) or request a higher quota / add credits.
Account not eligibleCheck the account requirements in section B (e.g. business/professional account, verified property, registered organisation).
App review requiredPermissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions.
Billing requiredAdd a payment method or prepaid credits on the provider account (see section E).

JDisconnect & security

Revoke access at the provider
LinkedIn → Settings → Data privacy → Permitted services → remove the app. Generate a new Client secret on the app's Auth tab to rotate.
Disconnect in the application
App → Integrations → Providers & API keys or App → Integrations → Connected accounts → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
Rotate credentials
Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
How credentials are stored
Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
What data the application can access
Profile basics, your posts and (with approval) company Page posts, comments and statistics.

Other Social providers

Start Free