SocialOAuth 2.0 — Client ID + Client secretPricing verified 2026-10-06
Publish to LinkedIn profiles and company pages, read comments and post statistics; base app for LinkedIn Ads.
AProvider definition
- Provider
- 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)
- Official site
- https://www.linkedin.com/developers/apps
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
- 1linkedin.com/developers/apps → Create app; associate it with your company Page and verify it from the Page.
- 2Products: add “Sign In with LinkedIn using OpenID Connect” and “Share on LinkedIn” (personal posting).
- 3For company-page posting and comments, request the “Community Management API” product (separate review).
- 4Auth tab: add the Authorized redirect URLs shown below; copy the Client ID and Client secret.
- 5Enter them in the application. After Community Management approval, add the organisation scopes to the Scopes field.
- 6Connect accounts from Integrations → Connected accounts.
DPermissions & API scopes
| Scope / permission | Why it's needed | Requested by |
|---|---|---|
| openid | Sign the user in (OpenID Connect). | Default (personal profile) |
| profile | Read the member's name and photo. | Default (personal profile) |
| Identify the connected member. | Default (personal profile) | |
| w_member_social | Publish posts as the member. | Default (personal profile) |
| w_organization_social | Publish posts as a company Page (needs Community Management API). | Company pages (after Community Management API approval) |
| r_organization_social | Read company Page posts and comments. | Company pages (after Community Management API approval) |
| rw_organization_admin | List 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_social | Read company Page posts and comments. | LinkedIn Ads connection |
| w_organization_social | Publish 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.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Screenshot to add3. Project / app creationCreating the app or project used for this integration.
- Screenshot to add4. API enablementThe API or product enabled for the project.
- Screenshot to add5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Screenshot to add7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe 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.
| Field | Required | Example / default | Notes |
|---|---|---|---|
| Client ID | Yes | — | |
| Client secret | Yes | •••••••• | Stored encrypted; shown masked after saving. |
| LinkedIn-Version header (YYYYMM) | Optional | 202509 | |
| Scopes | Optional | openid profile email w_member_social | Add 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
- 1Connect your LinkedIn profile and publish a test post.
- 2After Community Management approval, connect a company Page and publish to it.
ITroubleshooting
| Problem | What to do |
|---|---|
| unauthorized_scope_error | The 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 listed | Add rw_organization_admin (after approval) and make sure the member is a Page admin. |
| Posts fail after ~60 days | Access tokens expire; reconnect the account. |
| Invalid credentials | Check the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure. |
| Missing permissions | Reconnect 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 failure | Sign-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 mismatch | Copy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| App review required | Permissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions. |
| Billing required | Add 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
Facebook / Meta
OAuth 2.0 (Facebook Login) — App ID + App secret
Setup guide Instagram
OAuth 2.0 through the Meta app (Facebook Login)
Setup guide Threads
OAuth 2.0 — Threads app ID + secret
Setup guide X (Twitter)
OAuth 2.0 with PKCE — Client ID + Client secret (+ app bearer token for listening)
Setup guide YouTube
OAuth 2.0 (Google) + optional API key
Setup guide TikTok
OAuth 2.0 — Client key + Client secret
Setup guide 
