client-reports

POST /v1/client-reports/brands/{brand_id}/reply-to/code

E-mail a confirmation code to the look's reply-to address.

All client-reports endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the sites.create 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/client-reports/brands/{brand_id}/reply-to/code \
  -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

⛔ Pro and Agency only (own_sender). Replies to a report reach the reply-to address only once it is confirmed, so a report can never tell a client to reply to an address nobody proved they read. Requires sites.create.

Parameters

NameTypeRequiredWhat it is
brand_id (path)stringYes—

Response

NameTypeRequiredWhat it is
sent_tostringYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429