client-reports

POST /v1/client-reports/clients/{client_id}/logo

Upload the client's own logo, printed beside "Prepared for" on its reports.

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/clients/{client_id}/logo \
  -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

Zinn® SEO stage E5. The same vetting and store as a brand logo (PNG, JPEG or WebP, size and dimension limits). Frozen onto every report made afterwards, so an old report keeps the mark it was sent with. Requires sites.create.

Parameters

NameTypeRequiredWhat it is
client_id (path)stringYes—

Response

NameTypeRequiredWhat it is
idstringYes—
namestringYes—
brand_idobjectYes—
logo_sha256stringYesThe client's own mark (E5); empty when none.
domainsstring[]Yes—
recipientsstring[]Yes—
localestringYes—
sectionsClientReportSectionKey[]Yes—
contact_namestringYes—
notesstringYes—
cadenceClientReportCadenceYes—
send_emailbooleanYes—
narrativebooleanYeszs-541: reports open with a summary in plain words.
activebooleanYes—
next_run_atobjectYes—
last_run_atobjectYes—
created_atstringYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429