LinkedIn API

LinkedIn API for scheduling company pages and profile posts

A LinkedIn API that handles version headers, media registration, and company page permissions, so publishing stays one request.

Publish LinkedIn content from your SaaS product, agency workflow, or internal tool without rebuilding version headers, permissions, media uploads, and company page handling.

Last updated: July 2026

View API docs

One API key. No per-account fees. 15 platforms.

API key authScheduled publishing15 platforms

Quick start

API request

1const response = await fetch("https://api.bundle.social/api/v1/post", {2  method: "POST",3  headers: {4    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5    "Content-Type": "application/json"6  },7  body: JSON.stringify({8    teamId: "team_123",9    title: "LinkedIn thought leadership",10    postDate: "2026-05-13T08:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["LINKEDIN"],13    data: {14      LINKEDIN: {15        text: "What we learned building social media infrastructure for SaaS teams.",16        link: "https://bundle.social/blog/social-media-api-architecture-guide"17      }18    }19  })20});

Official APIs500k+ connected accountsDirect engineer support

LinkedIn API direct

LinkedIn access depends on permissions, product approval, member roles, and versioned API headers.

Company page publishing needs the right admin relationship and channel mapping.

Media, link previews, privacy settings, and document or video titles add product-level complexity.

B2B customers expect reports and status, not just a successful HTTP request.

What bundle.social handles

Use a simple post creation flow with LinkedIn-specific text, link, media, privacy, and reshare settings.

Schedule LinkedIn posts alongside X, Instagram, Facebook, Threads, and other platforms.

Use analytics and post history where the connected account and LinkedIn permissions support it.

LinkedIn API details quickly become customer-facing

Company page access, member roles, and versioned API behavior can turn into support tickets. bundle.social keeps those details connected to scheduling, status, and reporting before they reach your customers.

Workflow

How it works

Connect accounts once, then create and schedule posts with channel-specific fields from one API.

Create an API key

Generate an organization API key in the dashboard and use it with the x-api-key header.

Connect accounts

Connect each social account once. bundle.social keeps the account mapping ready for future posts.

Create or schedule posts

Send one request with the publish date, selected channels, and the fields each platform needs.

Product architecture

Build social media workflows without rebuilding every platform

LinkedIn API for B2B publishing workflows

B2B SaaS products, agencies, employee advocacy tools, developer relations teams, and internal marketing systems get the most out of a LinkedIn API integration. These teams need company page posts, profile posts, links, documents, videos, approval workflows, and reporting context. They also need to respect LinkedIn roles, permissions, versioned API behavior, and organization access.

bundle.social gives LinkedIn a production publishing workflow without forcing your team to own every native API detail. Your backend can create scheduled posts, attach media or documents, include links, target connected accounts, and keep status visible alongside other social channels. LinkedIn-specific fields remain available, but the surrounding account, scheduling, and support model stays shared.

Company pages, profiles, documents, and links need explicit product design

LinkedIn is not just another text box. A customer may want to publish to a company page, a personal profile, a document post, a video post, or a link preview. Each workflow has different eligibility, account context, media requirements, and reporting expectations. If those differences are hidden, they usually appear later as failed posts or confusing support tickets.

A better LinkedIn publishing flow makes account type, payload shape, media attachments, privacy controls, and status visible before publish time. bundle.social helps product teams keep that structure while still using the same API patterns for Instagram, Facebook, TikTok, YouTube, X, Google Business Profile, and other channels.

LinkedIn reporting as part of the broader social stack

B2B teams often care about what happened after a LinkedIn post goes live: impressions, engagement, post history, campaign context, and account-level performance where the platform exposes it. If LinkedIn reporting is built separately from publishing, it becomes harder to connect content decisions to business workflows.

By keeping LinkedIn publishing, status, post history, and analytics near the rest of the social media API, bundle.social gives SaaS and agency teams a stronger foundation for customer dashboards and internal reporting. LinkedIn becomes part of the same measurable campaign workflow instead of a separate native integration with separate operational rules.

Capabilities

LinkedIn publishing for B2B products and agency workflows

Schedule company page and profile posts with the LinkedIn fields that matter, without the API maintenance.

Company page and profile posting

Publish to LinkedIn personal profiles and company pages from the same workflow once accounts are connected and permissions are granted.

Link previews and articles

Include an optional link field to generate LinkedIn link preview cards for blog posts, press releases, and product pages.

Documents and video

Schedule LinkedIn document posts (PDFs, presentations) and video content using upload IDs from the media library.

Privacy and reshare controls

Set LinkedIn privacy settings and reshare options at post creation time for content that needs audience restrictions.

Analytics and post history

Pull LinkedIn performance data and import post history for connected accounts where permissions allow.

Dashboard for marketing teams

Non-technical teammates can review scheduled LinkedIn content in the same calendar as Instagram, X, and other channels.

Platform specifics

LinkedIn API specifics for B2B publishing

LinkedIn treats personal profiles and organization pages differently, which affects publishing, analytics, and customer support.

Personal vs organization

Personal profiles have limited API access and cannot import post history. Organization pages support richer analytics and historical import.

URNs are the data model

LinkedIn identifies people and companies with URNs such as urn:li:person and urn:li:organization. Advanced mentions and targeting need to respect that model.

B2B media limits

LinkedIn text supports up to 3,000 characters, media titles up to 200 characters, videos up to 1 GB, and documents as PDF files up to 100 MB.

Developer example

Schedule a LinkedIn post

Examples use bundle.social's public API shape: API key authentication, a post date, selected social account types, and platform-specific data.

TypeScript

API request

1const response = await fetch("https://api.bundle.social/api/v1/post", {2  method: "POST",3  headers: {4    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5    "Content-Type": "application/json"6  },7  body: JSON.stringify({8    teamId: "team_123",9    title: "LinkedIn thought leadership",10    postDate: "2026-05-13T08:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["LINKEDIN"],13    data: {14      LINKEDIN: {15        text: "What we learned building social media infrastructure for SaaS teams.",16        link: "https://bundle.social/blog/social-media-api-architecture-guide"17      }18    }19  })20});

Supported content

Text postsLink previewsImagesVideosDocumentsPrivacy settingsCompany pages

Honest limitations

LinkedIn permissions and company page roles still decide which accounts can publish.
Some advanced LinkedIn products are approval-gated or partner-gated.
Versioning and platform policy remain LinkedIn-controlled even when bundle.social simplifies the workflow.

Guarantees

Developer-first infrastructure

Visible post status

Track scheduled, processing, posted, retrying, and error states per post.

Verbose errors

When native APIs fail, we return human-readable error messages and actionable recovery steps.

Flat pricing

No per-post counting. Predictable pricing for teams managing many users, workspaces, and connected accounts.

Same-day support

Direct access to the engineers building the API. We respond to technical issues the same day, sometimes the same hour.

FAQ

Questions developers ask before building

Can I schedule LinkedIn posts through bundle.social?

Yes. Create a scheduled post with socialAccountTypes set to LINKEDIN and provide LINKEDIN-specific text, link, upload IDs, or privacy options.

Does this work for company pages?

bundle.social supports channel-based account workflows, but LinkedIn company page access still depends on the connected user's page role and granted permissions.

Can I include links in LinkedIn posts?

Yes. The LINKEDIN payload supports an optional link field for article or link preview posts.

Can I track LinkedIn analytics?

LinkedIn analytics are available when account permissions and API access allow them.

Why not build directly on LinkedIn's API?

You can. bundle.social is a better fit when LinkedIn is one of several platforms and you also need scheduling, media, analytics, post history, and a usable dashboard.

LinkedIn API errors

Troubleshoot LinkedIn publishing failures, permissions, media validation, rate limits, and retry decisions.

LinkedIn Scheduler

See the workflow and calendar view for LinkedIn content teams.

Social Media Analytics API

Report on LinkedIn and other supported channels.

Media Upload API

Attach images, videos, and documents to LinkedIn posts.