ads

POST /v1/ads/connections/{connection_id}/linkedin/changes

Pause, resume, re-budget or re-bid one LinkedIn campaign — the click is the approval (LIFULL).

All ads endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the ads.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/ads/connections/{connection_id}/linkedin/changes \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "action": <string<pause, enable, budget, bid>>, "campaign_id": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Gated on ads.manage; audit action ads.linkedin_change. The request is built from the campaign as LinkedIn holds it now, proposed and approved in one step, then sent by the apply workflow through the same gate as every write (kill switches, good standing, the spend ceilings weighed against the serving campaigns' daily budgets), with a 30-day Undo that puts back exactly what LinkedIn held. amount_micros is the new daily budget (budget) or bid (bid) in micros of the campaign's currency. Refusals (422): noSuchConnection, linkedinNeedsWriteScope (the grant is read-only: reconnect), noSuchAd (no such campaign), linkedinNotEditable (no budget or bid of its own, a bad amount, nothing would change, or the request carries a placements key: placement changes are never sent, so such a request is refused whole), killed, paused, disconnected, notInGoodStanding, needsReconnect and linkedinReadFailed (reading the campaign from LinkedIn failed; nothing is kept or sent). LinkedIn's Development Tier accepts changes only on the ad accounts listed on our app; a change it refuses fails on the change itself with linkedinWriteNotAllowed.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Request body

NameTypeRequiredWhat it is
actionstring<pause, enable, budget, bid>Yes—
campaign_idstringYes—
amount_microsintegerNoThe new daily budget or bid in micros of the campaign's currency (1 unit = 1,000,000).

Response

NameTypeRequiredWhat it is
idstringYes—
org_idstringYes—
connection_idstringYes—
action_classstringYes—
statusAdsChangeStatusYes—
summaryobjectYesWhat the change does, for the card. SERVEWATCH adds serving_check (a bid-strategy switch simulated before the send: verdict ok · unknown · starves, strategy, reason,…
budget_delta_minorobjectYes—
proposed_bystringYesWho proposed the change: who stored it (user:<id>, autopilot, mcp:<id>, apikey:<id>, …) — except a member of our staff, who reads support and never their id…
proposed_by_kindobjectYesPROPOSERKIND: who proposed the change, as a kind the screen translates — the same words as a decision's decided_by_kind. person a member of this account's org; agency a…
proposed_atstringYes—
decided_bystringYesWho approved or declined it (autopilot when the audit made it by itself; a person who applied the audit's one-click suggestion is named here although proposed_by stays…
decided_atobjectYes—
applied_atobjectYes—
undoablebooleanYes—
undo_untilobjectYes—
undone_atobjectYes—
errorstringYesWhy the change was not sent, its CODE leading (ceiling, killed, paused, holdReleased — GATE-PERSON r10: kept for a person while its campaign was held, and the hold was…
decision_reasonstringNoza-104: the reason given with the decision. An agency's client must give one to reject on the approval portal; decided_by then reads…

Errors this endpoint can return

401 · 403 · 404 · 422 · 429