Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
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
| Name | Type | Required | What it is |
|---|---|---|---|
sha256 (path) | string | Yes | — |
Errors this endpoint can return
404