client-reports

POST /v1/client-reports/clients/{client_id}/portal-links

Make a link to the client's own page of reports, under the agency's brand.

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

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

One address the client bookmarks once: every ready report made for them appears there, newest first, with its PDF. Read-only, white label, noindex. Optionally expiring (1 to 3650 days); at most 20 live links per client. Requires sites.create.

Parameters

NameTypeRequiredWhat it is
client_id (path)stringYes—

Request body

NameTypeRequiredWhat it is
labelstringNoThe agency's own note. Never shown to the client.
expires_in_daysobjectNo—

Response

NameTypeRequiredWhat it is
idstringYes—
client_idstringYes—
labelstringYes—
urlobjectYesnull once revoked or expired.
livebooleanYes—
expires_atobjectYes—
revoked_atobjectYes—
viewsintegerYes—
last_viewed_atobjectYes—
created_atstringYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429