LinkedIn opens post boosting to third-party apps with a new Boost API

LinkedIn's October 2026 Marketing API release adds a Boost API, so apps can now turn a member's or a Company Page's existing post into a paid ad. It affects anyone who schedules LinkedIn posts with a third-party tool, and the developers who build those tools.

What this means for you

Boosting means paying LinkedIn to show a post you already published to more people. Before this change, you had to open LinkedIn to do it. Now the tool you plan and publish with is allowed to offer the same Boost button, show you an estimate of reach and cost, and report how the boost did.

There is a catch: each tool must be approved by LinkedIn for its Advertising API before it can offer this. So the change opens a door; it doesn't put a button in your scheduler today. LinkedIn's own post boosting works exactly as before.

The details

LinkedIn describes the purpose plainly in its release notes: the endpoints "enable partners to embed LinkedIn Boosting directly into their content and publishing workflows." They are available under the existing Advertising API product, starting with version 202610.

There are two parallel sets of endpoints. Member endpoints start with member and boost the signed-in person's own posts. Organization endpoints start with organization and boost posts on a Company Page the person can manage.

The flow runs in five steps:

1. Status checks whether a post can be boosted and says why not when it can't. For a post that has a boost, it reports whether it is running, in review, scheduled or finished.
2. Init finds or creates the ad account and billing setup that will pay for the boost. If billing isn't set up, the app sends the user to a LinkedIn billing page and calls init again afterwards.
3. Hydrate previews targeting, forecast and price for a budget and objective. After the first call, the user can change only the objective, run schedule and budget.
4. Post creates the campaign group, campaign and creative that make up the boost.
5. Analytics returns results for boosted posts through a shared /boostAnalytics endpoint.

A separate call stops a running boost. Permissions are new too: r_member_boost and rw_member_boost for member posts, r_organization_boost and rw_organization_boost for Company Page posts.

One detail matters for schedulers that publish on behalf of people. LinkedIn notes that reading member posts back requires r_member_social, which is closed access. So an app has to keep the post ID it got when it published the post with w_member_social. A scheduler that never stored those IDs can't easily offer boosting for older posts.

The full technical breakdown is in our changelog entry: LinkedIn adds Boost API. Everything else that changed for LinkedIn publishing is on the LinkedIn hub.

What to do next

• Business owners: Nothing. Keep boosting in LinkedIn if you already do.
• Marketers and agencies: If you boost client posts every week, ask your scheduler whether LinkedIn boosting is on its roadmap. It would save switching between tools and keep results next to your organic numbers.
• Developers: Apply for the Advertising API with the boost scopes, send Linkedin-Version: 202610 or later, and start storing post URNs at publish time.

Also on LinkedIn's calendar: Marketing API version 202511 sunsets on November 16, 2026. Any integration still sending that version header needs to move to a newer one this month.