ads

POST /v1/ads/connections/{connection_id}/matching-pages/{page_id}/write

Write (or rewrite) the page with the AI writer (za-N6).

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}/matching-pages/{page_id}/write \
  -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.manage, audit-logged. A Temporal workflow reads the site's own pages and writes the headline, intro, points and button, every line citing the sentence it restates (no invented price or claim), then translates it into the site's other languages in one batched call. Spends AI credit on the organisation's own meter; an organisation not in good standing is refused before any spend (422 landingNotInGoodStanding), and a run already started stops before the writer.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—
page_id (path)stringYes—

Response

NameTypeRequiredWhat it is
dataAdsMatchingPageYesOne matching landing page for one ad group on a site hosted with us (za-N6, docs/1006 §94).

Errors this endpoint can return

401 · 403 · 404 · 422 · 429