ads

GET /v1/ads/connections/{connection_id}/experiments

The account's dated budget tests (za-193).

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}/experiments \
  -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. Every budget test of the connection, newest first: its state (awaiting_approval, starting, running, ended, failed, or the change's own status once rejected or undone), the campaigns with their budget before and during the test, the step in percent, the days, its change and — once applied — its dated review with the verdict and the keep / revert / extend offer. supported is false for a network other than Google Ads; campaigns are the campaigns with stored figures a new test can cover. Read from our own rows — never a network call (docs/1006 §69). The same rows answer the MCP tool ads_experiment_read.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
supportedbooleanYes—
dataAdsExperiment[]Yes—
campaignsobject[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 429