LinkedIn Scheduler

LinkedIn scheduler for B2B products and company pages

Publish to every LinkedIn company page and founder profile your product or your team posts to from one calendar, with admin roles and media registration resolved per account rather than per login.

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

1await 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 campaign",10    postDate: "2026-05-14T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["LINKEDIN"],13    data: {14      LINKEDIN: { text: "Scheduled from bundle.social." }15    }16  })17});

Official APIs500k+ connected accountsDirect engineer support

What native LinkedIn publishing leaves to your team

LinkedIn is high-value for B2B teams, but page roles, member permissions, media formats, link previews, and reporting all add friction.

What bundle.social handles

Plan LinkedIn thought leadership, company updates, and launch posts in the same calendar as every other channel.

Keep LinkedIn in the same workflow as every other channel

B2B teams can't afford a wonky company page permission killing a Thursday morning post. Keep LinkedIn in the same calendar as the rest of the campaign and stop babysitting it.

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.

We register media before the post

LinkedIn requires media to be registered and uploaded before the post references it, and member posts and company page posts use different endpoints and roles. You send one request; bundle.social registers the asset and routes to the right author.

Product architecture

Build social media workflows without rebuilding every platform

LinkedIn scheduler for B2B content and company pages

For B2B SaaS products, technical founders, and the agencies and marketing teams they serve, LinkedIn carries the highest stakes per post and the most friction around it. Company updates, founder posts, documents, link previews, videos, and approval steps all depend on page roles and member permissions a generic calendar does not model.

bundle.social holds LinkedIn planning, review, and publishing in one workspace. Company page updates stay separate from personal thought leadership, documents and media attach cleanly, and approvals stay attached to the scheduled post rather than to a chat thread.

Company updates and founder posts are different workflows

A company page post and a founder post reach different audiences, need different tone, and often need different approvers. They also depend on different permissions, since company page publishing requires an admin role held by the person who connected the account.

Both live in the same bundle.social calendar with that distinction preserved, so B2B teams can plan a launch as a coordinated set instead of as separate accounts managed by separate people. Company page access still depends on LinkedIn roles and granted permissions, so those limits stay visible before publish time.

A launch is a company update, a founder post, and an X thread

B2B campaigns rarely stop at LinkedIn. A launch usually includes a company page update, a founder post, an X thread, a newsletter, and a changelog, and leadership asks how the whole set performed rather than how one post did.

LinkedIn scheduling, approvals, delivery status, post history, and analytics where LinkedIn exposes them sit next to every other channel. Agencies get one reporting view per client, and the same workflow moves to the API when publishing has to be automated.

Let your own users connect their LinkedIn accounts

LinkedIn needs watching after the connection succeeds: company page publishing depends on an admin role held by the person who connected, so the set of pages a connection can post to changes whenever the client reorganizes page permissions.

You generate a hosted portal link, your user connects their own LinkedIn account through it, and bundle.social stores and refreshes the token. The link carries your branding, expires on a window you set between 5 minutes and 48 hours, and means you never implement LinkedIn API OAuth yourself. Publishing from your own code instead of the dashboard uses the same connected accounts.

Capabilities

LinkedIn scheduling with the workflows your team already uses

LinkedIn fits into the same scheduling, media, and status workflow as every other channel.

LinkedIn in your cross-platform calendar

Plan and schedule LinkedIn content alongside Instagram, LinkedIn, X, TikTok, and every other channel without switching between native dashboards.

Channel-specific field control

LinkedIn content still uses the options and fields the platform supports. No generic template that loses native capabilities.

Team review and approvals

Marketing teams can draft, review, and approve LinkedIn content in the shared calendar before anything publishes.

Media library for campaigns

Upload visuals, videos, and documents once and attach them to LinkedIn posts using upload IDs across your content plan.

Post status tracking

See whether each LinkedIn post is scheduled, processing, posted, or failed without checking the native platform dashboard.

Analytics where available

Pull LinkedIn performance data and import post history for connected accounts where the platform API and permissions allow it.

Company page and profile planning

Separate company updates, founder posts, and profile-led thought leadership while keeping approvals in the same campaign calendar.

Documents and B2B assets

Coordinate PDFs, link previews, videos, and image posts with the approvals B2B teams need before launch.

Developer example

Schedule LinkedIn content

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

1await 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 campaign",10    postDate: "2026-05-14T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["LINKEDIN"],13    data: {14      LINKEDIN: { text: "Scheduled from bundle.social." }15    }16  })17});

Supported content

Profile postsCompany pagesLinksImagesVideosDocuments

Honest limitations

Company page access depends on LinkedIn roles and granted permissions.

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

Why did publishing to one LinkedIn company page stop working?

Company page publishing depends on an admin role on that page, held by the person who connected the account. That role belongs to the client organization, so it disappears when the person leaves or when someone reorganizes page permissions. It fails for one page while every other page keeps working, which is how you tell it apart from a token problem that fails everything at once.

Are founder profiles and company pages the same thing to the API?

No. LinkedIn treats member profiles and organization pages as separate endpoints with separate permissions, so content written for one is not automatically publishable as the other. Both can sit in the same calendar, which is the point, because the coordination problem between them is editorial rather than technical.

Why does our LinkedIn link post have no preview image?

LinkedIn builds the preview from the destination URL, not from anything in the post payload, so a missing preview almost always means the destination page lacks correct Open Graph tags. Across many client pages a missing preview usually points at the client's own site rather than at the scheduler.

Why use bundle.social for LinkedIn instead of the native scheduler?

Because the native scheduler cannot tell you that one client's company page quietly lost its admin role, and that is the failure that matters when you publish to more than a couple of pages. bundle.social registers media before the post, routes member and organization posts to the right endpoint, and reports a lost page role separately from a token problem, so the person who can fix it hears about it.

Can our own users connect their own LinkedIn accounts?

Yes. You generate a hosted portal link carrying your own branding, and bundle.social stores and refreshes the LinkedIn token, so a reconnect is something your user can do without a support ticket.

Can LinkedIn run in the same calendar as our other channels?

Yes, and the per-platform differences stay per platform. One scheduled post can target several channels at once, with a LINKEDIN object carrying only the fields LinkedIn needs.

LinkedIn API

Go deeper on the developer workflow.

LinkedIn API errors

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

Schedule Posts

See how cross-platform scheduling works.

Analytics API

Review reporting and post history options.