ads

GET /v1/ads/connections/{connection_id}/merchant-feed

The account's Shopping + Merchant Center feed audit (za-188).

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}/merchant-feed \
  -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 settings and the last daily audit of the product feed: products the network disapproved or limited (missing GTIN, price or availability mismatch, policy, landing page), our own landing-page read of every product that spent, out-of-stock products still spending (linked to the stock pause), and product-level waste — spend with no sale over the threshold (the customer's own, or Recommended: the account's own cost per sale) — with each exclusion queued for approval. Read from our own row; the audit runs in the connection's daily Temporal child, never in the request (docs/1006 §80).

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
dataAdsMerchantFeedYesza-188 (docs/1006 §80): a connection's Shopping feed audit. result is the last daily audit (empty before the first): counts (whole, never capped), threshold…

Errors this endpoint can return

401 · 403 · 404 · 429