GET /v1/branding/logo/{sha256}

Autentifikacija

Pošaljite API ključ kao bearer token. Ova krajnja tačka ne navodi specifičnu dozvolu u specifikaciji, zato dodelite svom ključu minimum potrebnih ovlašćenja i proverite odgovor umesto da pretpostavljate.

Ovaj krajnji tačka ne prihvata ID organizacije. Vaš ključ već identifikuje organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamenite bilo šta u uglastim zagradama sopstvenim vrednostima, a ključni placeholder sa ključem sa vaše kontrolne table.

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

Prijavljeni ste? API konzola na vašoj kontrolnoj tabli automatski popunjava ID vaše stvarne organizacije i vaš sopstveni ključ, i izvršava zahtev nad API-jem uživo tako da možete videti stvarni odgovor. Otvorite ovu krajnju tačku u API konzoli

Detalji

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.

Parametri

Greške koje ovaj krajnji tačka može da vrati

404