Skip to content
Schedule Social Media

Press Esc to close.

Breaking LinkedIn Severity: medium

LinkedIn Boost API 202611: saved audiences, boost management, hosted billing, per-campaign analytics

AnnouncedNov 2026
EffectiveNov 2026
PlatformLinkedIn

What changed

LinkedIn's November 2026 Marketing API release (version 202611) extends the Boost API launched in October. Targeting is simplified to includeAll, excludeAny and anyOf criteria, Boost Init returns targetingEntities and accepts a locale, and /rest/boostTargetingCriteria creates, finds, updates and deletes saved audiences. New Boost Manage resources retrieve a boost's details, targeting, budget, schedule and forecast, let partners edit only targeting and the political declaration, and delete boosts; the legacy delete resources are deprecated. Init now always returns a LinkedIn-hosted billingUrl, and billingConfigured reflects billing readiness. Boost Post actions accept a politicalIntent declaration. Breaking: Boost Analytics returns metrics per campaign in a campaigns array, with spendInLocalCurrency, instead of flat post-level fields with USD spend. LinkedIn revised these notes on November 20, 2026.

What it means

Apps that boost LinkedIn posts gain simplified targeting and saved audiences, read, edit and delete for live boosts, a LinkedIn-hosted billing link and a political-intent declaration in version 202611. Boost Analytics changes shape: metrics now come per campaign, with spend in local currency.

Who is affected

Schedulers and publishing tools that offer the LinkedIn Boost API for member or Company Page posts, and agencies boosting client posts through them.

What to do by Nov 2026

When moving Boost calls to Linkedin-Version 202611, read analytics from the new campaigns array, move delete calls to the Boost Manage resources, and send advertisers to the returned billingUrl instead of collecting payment details.

What this means for you

Some scheduling apps let you pay to boost a LinkedIn post without leaving the app. From LinkedIn's November 2026 update, those apps can let you pick or save the audience, see and change who a running boost reaches, or stop and remove it. Billing happens on a LinkedIn page the app sends you to. Boost results now come per campaign, with spending in your own currency.

The details

  • Version: all changes need Linkedin-Version: 202611. The Boost API itself arrived in 202610: see LinkedIn adds Boost API.
  • Targeting: Member and Company Page Boost APIs use simplified criteria: includeAll (all must match), excludeAny (excludes matching members) and anyOf (alternative values within a criterion). Boost Init returns targetingEntities with the supported facets and options, and Init and Hydrate accept an optional locale. The shared /rest/boostTargetingCriteria resource creates, updates and deletes saved audiences and finds them by ad account; creation needs an ad account, a name and location targeting.
  • Managing boosts: /rest/memberBoostManage/{campaignId} and /rest/organizationBoostManage/{campaignId} retrieve a boost's campaign details, targeting, budget, schedule, political declaration and forecast, or delete the boost. "Only targetingCriteria and politicalIntent are editable"; budget, objective and schedule aren't. The legacy memberBoostCampaign and organizationBoostCampaign delete resources are deprecated but still work in 202610 and 202611.
  • Billing: from 202611, Init returns billingUrl "regardless of whether billingConfigured is true or false". Open it exactly as returned. LinkedIn says partners "should not collect payment details themselves". billingConfigured reflects billing readiness, and accounts on billing hold return false: complete setup or resolve the hold, then call Init again.
  • Political intent: Member and Company Page Boost Post actions accept a politicalIntent declaration, and Boost Hydrate can return politicalDeclarationRequired. "An absent value isn't a confirmed false." LinkedIn's ban on political advertising is unchanged.
  • Breaking, Boost Analytics: boostAnalytics returns metrics by campaign in a campaigns array, including spendInLocalCurrency in each ad account's currency, instead of post-level totals with spend in USD. Read the new structure when upgrading from 202610, and "don't combine monetary amounts with different currencies". Metrics cover up to two years; approximateMemberReach is the highest per-campaign reach over a window of up to 91 days. (LinkedIn's first version of these notes, on November 16, said campaign metrics weren't populated yet; the November 20 revision no longer says so.)
  • Not covered here: the release's ads-only changes (Ad Accounts billingReference, Conversions API SHA256_PHONE, publisher-list surface, EU political declarations for campaigns from December 15, 2026).
  • Version dates: 202611 is supported until November 16, 2027; see the sunset calendar.

What to do next

  • Business owners: Nothing. If you boost posts from a scheduler, finish billing on LinkedIn's page when the app asks.
  • Marketers and agencies: Boost spend in tools on 202611 is reported per campaign in each ad account's own currency, so don't add up figures from accounts in different currencies.
  • Developers: Read Boost Analytics from the campaigns array, move delete calls to the Boost Manage resources, open billingUrl exactly as returned, and treat a missing politicalIntent as undeclared.

Primary sources

Checked against the source 21 Nov 2026

Get an email when a new API change is added

Follow new entries with the RSS feed. Each platform also has its own feed, for example X or Meta.