ads

GET /v1/ads/connections/{connection_id}/linkedin/campaigns

A LinkedIn ad account's campaigns with status, daily budget, bid and 7-day spend (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.view 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 GET https://api.zinndigital.com/v1/ads/connections/{connection_id}/linkedin/campaigns \
  -H "Authorization: Bearer zdk_live_…"

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.view. Read from LinkedIn now: every campaign that is not removed, with its status, whether it serves now, its daily and total budget and its bid (micros of the campaign's currency, null when it has none) and its spend over the last days days. write is the connection's linkedin_write (whether LinkedIn granted rw_ads, so a change can be sent). Refusals (422): noSuchConnection (not a LinkedIn connection), needsReconnect (LinkedIn refused the sign-in: revoked or expired), linkedinReadFailed (LinkedIn did not answer; the error carries the §2.57 failure class and, on an outage, LinkedIn's status board).

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
connection_idstringYes—
daysintegerYes—
currencystringYesISO 4217 code of the ad account.
writeobjectYes—
dataAdsLinkedinCampaign[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429