GET /v1/branding/logo/{sha256}

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Sehemu hii ya mwisho haitaji ruhusa maalum katika maelezo, kwa hivyo ipe ufunguo wako kiwango cha chini kabisa kinachohitajika na uangalie jibu badala ya kukisia.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

curl -X GET https://api.zinndigital.com/v1/branding/logo/{sha256} \
  -H "Authorization: Bearer zdk_live_…"

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

The image bytes for a logo digest. ⛔ **Unauthenticated, deliberately.** Its readers are a browser painting a panel, a browser painting a reseller's *sign-in* page — which by definition has nobody signed in — and a client's own panel. Requiring a token would break the login page, which is the surface where a reseller's mark matters most. ⭐ What stands in for authentication is the digest: this is a content-addressed store, so asking for an object means already knowing the sha256 of its exact bytes. There is nothing to enumerate, and the image is one the brand publishes on its own public login page anyway. ⭐ Immutable: the bytes behind a digest can never change, so the response is cacheable for a year and a new logo is simply a new URL.

Vigezo

Hitilafu ambazo mwisho huu unaweza kurudisha

404