Boost a Post

When you finish this page an existing Company Page post runs as a LinkedIn ad. You need a linkedinads account, the numeric ad account id from List ad accounts, and a published post.

Boost an existing post

Call POST /v1/ads/boost with postId, accountId, adAccountId, goal and budget. Zernio wraps the post in a fresh Campaign Group, Campaign and Creative, and the post keeps its social proof (reactions, comments) while it runs as an ad.

import Zernio from '@zernio/node';

const zernio = new Zernio();

const { data: boosted } = await zernio.adcampaigns.boostPost({
  body: {
    postId: '65f1c0a9e2b5af0012ab34cd',
    accountId: '66b2e19d8c3f5a7e9d0b1c2d',
    adAccountId: '517258773',
    name: 'Boost product launch',
    goal: 'engagement',
    budget: { amount: 50, type: 'daily' },
    schedule: { startDate: '2027-01-04T09:00:00Z', endDate: '2027-01-11T09:00:00Z' }
  }
});

console.log(boosted.ad._id);

Response (201):

{
  "ad": {
    "_id": "66f0a1b2c3d4e5f6a7b8c9d0",
    "name": "Boost product launch",
    "platform": "linkedin",
    "status": "pending_review",
    "adType": "boost",
    "goal": "engagement",
    "budget": { "amount": 50, "type": "daily" },
    "schedule": { "startDate": "2027-01-04T09:00:00Z", "endDate": "2027-01-11T09:00:00Z" },
    "platformCampaignId": "645412093",
    "platformAdSetId": "810456563"
  },
  "message": "Ad created and submitted for review"
}

schedule.startDate and endDate are date-times, not dates. To boost a post Zernio did not publish, send LinkedIn's own post id as platformPostId instead of postId, keeping the rest of the body identical:

{
  "platformPostId": "urn:li:share:7280421553219899392",
  "accountId": "66b2e19d8c3f5a7e9d0b1c2d",
  "adAccountId": "517258773",
  "name": "Boost product launch",
  "goal": "engagement",
  "budget": { "amount": 50, "type": "daily" }
}

Goals a boost accepts

goal takes 6 values on LinkedIn, every one the endpoint offers except app_promotion:

job_applicants is the one LinkedIn goal that boost does not take: it needs the jobs creative on POST /v1/ads/create.

Bidding options go in platformSpecificData, the same shape as on /v1/ads/create; see Bidding. Boost is not idempotent: send an Idempotency-Key header so a retry replays the original 201 instead of creating a second ad (Idempotency). Without the header an identical body is treated as a retry anyway: a 409 while one boost is in flight, and the ad already created within the last 10 minutes instead of a second one.

To sponsor an existing post under a campaign you build and control (choosing bidding, targeting and schedule the same way as any other format), use the thought-leader format on /v1/ads/create instead.

If it fails

A 422 on a boost is LinkedIn refusing to sponsor the post, most often because a personal profile authored it: LinkedIn's Marketing API sponsors organization-authored posts only. Zernio says so in error and passes LinkedIn's own rejection through in platformError:

{
  "error": "LinkedIn's API can't sponsor posts from personal profiles (Thought Leader Ads), only posts authored by an organization Page. Create member-post ads in LinkedIn Campaign Manager.",
  "type": "platform_error",
  "code": "platform_api_error",
  "platform": "linkedin",
  "platformError": {
    "status": 422,
    "errorDetails": { "inputErrors": [{ "code": "INVALID_URN_TYPE" }] }
  }
}

Boost a post the Company Page authored instead. A 422 whose platformError mentions organizationUgcAuthorizations is a different refusal: the post is a Company Page post nobody has approved for sponsorship, and the author approves it at linkedin.com/sponsorship-permissions. Take platformPostId from "Copy link to post", which gives the share or ugcPost id; a feed permalink carries an activity id, which LinkedIn does not sponsor.

Related

• Create ads: ads built from scratch, and bidding.
• Creative formats: thought-leader ads.
• Boost post: every field of the request.