identity

GET /v1/branding/font-file/{sha256}

One stored webfont file.

All identity endpoints

All developer docs →

Authentication

This endpoint takes no API key. Anything else it needs, such as a signed request, is described above.

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 GET https://api.zinndigital.com/v1/branding/font-file/{sha256} \
  -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

The woff2 bytes for a digest. The twin of GET /v1/branding/logo/{sha256}, content-addressed for the same reason: the digest is the identity, so the response is cacheable for a year and a different file is a different URL.

Parameters

NameTypeRequiredWhat it is
sha256 (path)stringYes—

Errors this endpoint can return

404