LinkedIn adds Boost API: turn member and Company Page posts into ads from your app

What this means for you

On LinkedIn you can pay to show a post you already published to more people. That's called boosting. Until now you had to do it inside LinkedIn. From October 2026, the apps you use to plan and publish posts are allowed to offer a Boost button too. The app has to be approved by LinkedIn first, so not every tool will have it.

The details

• Version: the endpoints arrive in Marketing API version 202610. Every Boost request needs the Linkedin-Version: 202610 header (or later) and X-Restli-Protocol-Version: 2.0.0.
• Access: your app must be approved for the Advertising API product. Community Management access alone is not listed as enough.
• Scopes: r_member_boost and rw_member_boost for a member's own posts; r_organization_boost and rw_organization_boost for Company Page posts. The read scopes cover status and analytics; the read-write scopes also cover init, preview and create.
• The flow, in order:
  1. Status (GET /rest/memberBoostStatus or organizationBoostStatus): is the post eligible, and if not, why. It also returns CURRENTLY_BOOSTED, IN_REVIEW, SCHEDULED or PREVIOUSLY_BOOSTED for posts with a boost.
  2. Init (POST /rest/memberBoostInit or organizationBoostInit): finds or creates the ad account and billing setup. If it returns billingConfigured: false, send the user to LinkedIn's billing page, then call init again.
  3. Hydrate (POST /rest/memberBoostHydrate or organizationBoostHydrate): preview targeting, forecast and pricing. Leave out totalBudget on the first call. After that the user can change only the objective, run schedule and budget, and you call hydrate again on each change.
  4. Post (POST /rest/memberBoostPost or organizationBoostPost): creates the campaign group, campaign and creative.
  5. Analytics (GET /rest/boostAnalytics): results for boosted member and Company Page posts.
• Stopping a boost: DELETE /rest/memberBoostCampaign (or organizationBoostCampaign) with the campaign and account URNs that status returns.
• Member posts: LinkedIn notes that reading member posts back needs r_member_social, which is closed. Your app must have created the post with w_member_social and kept the post ID.

What to do next

• Business owners: Nothing. Boosting in LinkedIn itself works as before.
• Marketers and agencies: Ask your scheduler whether it plans to support LinkedIn boosting, if you boost posts often.
• Developers: Apply for Advertising API access with the boost scopes and store post IDs when you publish, so you can boost them later.