ads

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

A Meta account's campaigns and spend over the last 30 days (za-40).

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}/meta/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. The stored reading (never a call to Meta in the request): reading is null until the first read finishes. figures carries currency, since, until, spend_micros (integer micros of the account currency) and campaigns[] (campaign_id, name, status, objective, spend_micros, impressions, clicks), biggest spend first; a campaign with no delivery is listed with zeros. A failed read replaces the figures with failure (the §2.57 class). A connection that is not Meta is a 422 refusal.adsconnect.campaignsNotOnNetwork (FIX13).

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
dataobjectYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429