ads

POST /v1/ads/connections/{connection_id}/relist

Add accounts from the sign-in this account was connected with.

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}/relist \
  -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

ADSUI1 (za-245). Gated on ads.manage; audit action ads.connection_relist. Lists again every ad account the connection's sign-in reaches now (accounts made at the network since appear), stores the list on that sign-in's grant and returns its id: the dashboard opens the ordinary account picker on it (GET /v1/ads/connect/{network}/grants/{grant_id}), where the accounts already connected are marked. grant_id is null when only a new sign-in can list them (the sign-in is gone, or the network refused its token).

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
grant_idobjectYes—
platformstring<google, microsoft, x, meta, chatgpt>Yes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429