ads

POST /v1/ads/client-approval-links

Make an approval link for a client org (za-104).

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.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

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/client-approval-links \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "org_id": <string> }'

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 on org_id (the CLIENT org); another org answers 404. days 1-30 (default 14, else badDays); label is the agency's own note (plain text, else badText). The 201 carries url once — only the token's SHA-256 is stored. Audit action ads.client_approval_link_created on the client org.

Request body

NameTypeRequiredWhat it is
org_idstringYes—
daysintegerNo—
labelstringNo—

Response

NameTypeRequiredWhat it is
idstringYes—
org_idstringYesThe CLIENT org the link reaches.
labelstringYes—
created_bystringYes—
created_atstringYes—
expires_atstringYes—
revoked_atobjectYes—
last_used_atobjectYes—
decisionsintegerYes—
livebooleanYes—
urlstringNoOnly in the 201 that made the link — the token is never stored and cannot be shown again. On the agency's own panel address once that address is live.

Errors this endpoint can return

401 · 404 · 422 · 429