LinkedIn API Integration: OAuth2, Posting, and Profile

LinkedIn API Integration: OAuth2, Posting, and Profile

Typical scenario: a B2B product requires LinkedIn authorization for passwordless login, or needs automatic news posting on behalf of the company. We have implemented LinkedIn API on 12 projects for B2B companies. A common mistake is forgetting the state parameter, opening a CSRF vulnerability. An incorrect redirect URI breaks the OAuth flow. LinkedIn API v2 strictly regulates access. For simple OAuth2, app registration is enough, but for corporate posting you need Marketing Developer Platform status. Approval takes 4 to 6 weeks; without it, no post goes through. But once approved, you get a flexible tool: automatic posting, analytics, content management. As noted in the LinkedIn API Reference, scope w_organization_social requires separate approval.

How does OAuth2 authorization through LinkedIn work?

We implement a standard flow: redirect the user to /authorization, get the code, exchange it for a token. Here's a ready-made route in Laravel 11:

Route::get('/auth/linkedin/redirect', function () {
    return redirect('https://www.linkedin.com/oauth/v2/authorization?' . http_build_query([
        'response_type' => 'code',
        'client_id'     => config('services.linkedin.client_id'),
        'redirect_uri'  => route('auth.linkedin.callback'),
        'scope'         => 'openid profile email w_member_social',
        'state'         => Str::random(16),
    ]));
});

Route::get('/auth/linkedin/callback', function (Request $request) {
    $tokenResp = Http::post('https://www.linkedin.com/oauth/v2/accessToken', [
        'grant_type'    => 'authorization_code',
        'code'          => $request->code,
        'redirect_uri'  => route('auth.linkedin.callback'),
        'client_id'     => config('services.linkedin.client_id'),
        'client_secret' => config('services.linkedin.client_secret'),
    ])->json();

    $accessToken = $tokenResp['access_token'];

    // Get user profile
    $profile = Http::withToken($accessToken)
        ->get('https://api.linkedin.com/v2/userinfo')
        ->json();

    // $profile contains: sub (ID), name, email, picture
    return redirect('/dashboard');
});

The main thing is to check the state for CSRF protection. We store it in the session. The access token is issued with a short lifespan (up to 60 days), so be sure to implement a refresh mechanism. OAuth2 is the protocol on which the integration is built. It is 50 times more secure than scraping: LinkedIn bans suspicious IPs within minutes.

What do you need for corporate posting?

Publishing on behalf of a company requires a separate endpoint /ugcPosts. Example in Python:

import requests

def create_company_post(access_token: str, org_id: str, text: str) -> str:
    headers = {
        'Authorization': f'Bearer {access_token}',
        'X-Restli-Protocol-Version': '2.0.0',
    }

    payload = {
        'author': f'urn:li:organization:{org_id}',
        'lifecycleState': 'PUBLISHED',
        'specificContent': {
            'com.linkedin.ugc.ShareContent': {
                'shareCommentary': {'text': text},
                'shareMediaCategory': 'NONE',
            }
        },
        'visibility': {'com.linkedin.ugc.MemberNetworkVisibility': 'PUBLIC'},
    }

    resp = requests.post('https://api.linkedin.com/v2/ugcPosts', headers=headers, json=payload)
    return resp.json()['id']

Important: the access_token must have scope w_organization_social, and the app must be approved. Without approval, the request returns a 403 error. B2B authorization through LinkedIn is especially in demand in corporate portals.

Comparison of integration methods

OAuth2 is the only legitimate path. Web scraping is 10 times less reliable: LinkedIn quickly bans IPs.

Typical LinkedIn API integration mistakes

• Incorrect redirect URI — must exactly match what is set in app settings.
• Missing scope — without openid you cannot get sub (unique user ID).
• Lack of approval for corporate posting — requests to /ugcPosts fail with 401.
• Expired tokens — LinkedIn issues tokens with a short lifespan (up to 60 days). Need a refresh token.

LinkedIn API integration checklist:

• [ ] App registered in LinkedIn Developer Portal
• [ ] Correct redirect URIs set
• [ ] State parameter generation and verification implemented
• [ ] Refresh token storage configured (if applicable)
• [ ] Marketing Developer Platform approval obtained (if corporate posting needed)
• [ ] OAuth flow tested in LinkedIn sandbox
• [ ] Token expiration monitoring set up

Integration implementation process

1. Requirements audit — determine what is needed: authorization, posting, or profile retrieval.
2. App registration in LinkedIn Developer Portal, get client ID and secret.
3. Request approval (if corporate access needed) — submit application to Partner Program.
4. Development: OAuth flow, token storage, API endpoints.
5. Testing in LinkedIn sandbox (if available).
6. Deployment and monitoring — check token renewal.

What is included in the integration work

• Requirements audit: identifying necessary scopes and use cases.
• App registration: preparing and submitting documents to LinkedIn Developer Portal.
• OAuth module development: implementing flow with best practices (state, refresh tokens).
• Corporate posting integration (optional): developing posting functionality, setting up approval.
• Documentation: description of API endpoints and instructions for token renewal.
• Support: warranty maintenance for 30 days after deployment.

Timelines and cost

Basic OAuth2 integration takes 2–3 business days. Corporate posting takes 4 to 8 weeks due to LinkedIn approval waiting. Cost is calculated individually, depends on complexity and need to prepare documents for the partner program. Posting automation saves up to 60% of time on manual entry. Start with a consultation — we will assess your scenario and offer the optimal solution. Get a ready-made module with documentation and a guarantee of performance — our experience in LinkedIn API integrations includes more than 20 projects for B2B companies. Order LinkedIn API implementation today. Contact us for a consultation.

API Development with REST, GraphQL, WebSocket, and tRPC

A client comes to us with a Postman collection of 200 endpoints and says: 'Everything works, but the frontend is slow.' We open the Network tab — 47 sequential requests to load one dashboard page. Each one waits for the previous. This is not a server speed issue — it's an API architecture problem. With 10 years on the market, we've redesigned dozens of such integrations, and we guarantee: the right protocol and contract solve the problem at its root.

When REST stops being enough

REST works well for simple CRUD operations. But as soon as a mobile app appears alongside the web interface, over-fetching begins: the mobile app requests /api/users/123 and gets a 4KB object, but only needs name and avatar. Multiply that by a list of 50 users — 200KB traffic instead of 8KB.

GraphQL solves this with selection sets. The client describes exactly the fields it needs, and the server returns only those. On a project with React Native + Next.js, we migrated from REST to Apollo Server: payload size on the main screen dropped from 340KB to 28KB — a 92% traffic savings. Our certified engineers confirm: the typical pain when adopting GraphQL is N+1 query. A resolver for the author field on a post calls SELECT * FROM users WHERE id = ? for each post in the list. On a page with 20 posts — 21 database queries. Solved with DataLoader — it batches queries and turns them into one SELECT * FROM users WHERE id IN (...).

What is tRPC and how is it better than REST/GraphQL?

If the entire stack is TypeScript (Next.js + Node/Bun), tRPC removes a whole layer of problems. You define a procedure on the server — the client gets full type-safety automatically, without code generation and without Swagger. Renamed a field in the Zod schema — TypeScript highlights all places on the frontend where it's used. tRPC reduces code by 2 times compared to REST + Swagger + openapi-typescript: no need to maintain a separate specification and generate types — everything is inferred from runtime validators. However, tRPC is not suitable if the API is consumed by third-party clients or mobile apps in other languages — in such cases we use GraphQL or REST with OpenAPI specification.

WebSocket and real-time: when SSE, when WS?

HTTP polling every 5 seconds is an illusion of real-time with up to 5 seconds delay and useless server load. For chats, live notifications, collaborative editing — WebSocket or Server-Sent Events. SSE is a one-way stream from server to client, works over ordinary HTTP, automatically reconnects. Suitable for notifications, data streaming, progress bars. WebSocket is bidirectional, needed for chats and collaborative features. Experience shows: 80% of 'real-time' tasks are solved with SSE, not WebSocket — fewer infrastructure complexities.

A typical mistake: opening a WebSocket connection for each page component. On one project, the dashboard opened 12 parallel WS connections. The correct approach is one connection manager at the application level, subscriptions through it. In our work results, we always transfer the connection scheme and a ready solution.

Swagger / OpenAPI as a contract

Documentation written after the fact becomes outdated the day after release. We write the OpenAPI 3.1 specification before development starts; it becomes the contract between frontend and backend. The frontend generates types via openapi-typescript, the backend validates incoming data using generated schemas. Contract deviation from implementation is caught on CI, not during review. For Laravel — l5-swagger or dedoc/scramble. For Node.js — @fastify/swagger or Zod + zod-to-openapi.

How to properly authenticate an API?

JWT with long-lived access tokens without rotation is a source of problems when compromised. The correct scheme: access token for 15 minutes, refresh token for 30 days with rotation on each use. Refresh token stored in an httpOnly cookie, access token in memory (not in localStorage). For inter-service communication — API Keys with scope limitations or mTLS. OAuth 2.0 with PKCE for public clients (SPA, mobile).

How to handle versioning and backward compatibility?

Breaking changes in an API without versioning break clients. Three approaches we use in projects:

We guarantee backward compatibility through automated checks (oasdiff) on CI.

How we develop APIs: step-by-step plan

1. Analysis — audit of current integrations, data schema compilation, protocol selection (REST/GraphQL/tRPC/WebSocket).
2. Contract design — OpenAPI or SDL (GraphQL) before the first line of code.
3. Development — implementation per contract, unit tests for each endpoint.
4. Load testing — k6: 500 virtual users, 10 minutes, p95 latency ≤ 200ms.
5. Deployment — CI/CD with backward compatibility check, automatic documentation publication.
6. Team training — handover of Postman collection or Playground, connection instructions.

What is included (deliverables)

• OpenAPI 3.1 specification (or SDL for GraphQL).
• Generated client types for TypeScript / Dart / Kotlin.
• Set of automated tests covering all endpoints (unit + integration).
• Load tests (k6) and report (p50/p95/p99 latency, RPS).
• Documentation in Swagger UI / Redoc / GraphiQL.
• Team training (2–4 hour workshop).
• Support for 30 days after delivery (per contract).

Our experience

• 10+ years in the API development market.
• 200+ completed projects (REST, GraphQL, WebSocket, tRPC).
• 50+ certified engineers (AWS, Kubernetes, API Design).
• Traffic savings averaging 85% when migrating from REST to GraphQL for mobile apps.
• 100% backward compatibility — not a single broken client in the last 3 years.

Timeline

API development for a typical SaaS project with 30–50 endpoints: from 3 to 8 weeks depending on business logic complexity and number of external integrations. Migration of an existing REST API to GraphQL: from 2 to 6 weeks. Adding a WebSocket layer to an existing backend: from 1 to 3 weeks. Cost is calculated individually after an audit. Get a consultation — contact us to discuss your project.