Typed SDKs, or
just a plain URL.
The API is plain HTTP, so the smallest integration is a single address — logos, variants, colors, kits, search and symbol lookup all included. When you want types, a client and a component that handles missing logos for you, there are two tiny packages.
Start with
a URL.
Nothing to install, nothing to configure. Every capability can be called straight from browser code — search included — without a server-side proxy in between.
Most teams never go past this. The packages below exist for the cases where types and a ready-made component genuinely earn their place.
A tiny typed client
Zero dependencies and fully typed. One helper builds a logo address without touching the network; the client wraps company lookups and search, and takes an optional key.
Reach for it when you want the compiler to catch a bad size or a misspelled field, and when company lookups and search are going through your own server rather than the browser.
One component, batteries included
Real logo when it exists, a deterministic letter tile when it doesn't — the colour is derived from the domain, so the same company always gets the same tile. The whole logokit client is re-exported, so one dependency covers both.
Reach for it when you are rendering companies in a React list and do not want to write the missing-logo case yourself — the component already handles the miss, the alt text and the lazy loading.
Full API reference.
Parameters, response schemas, headers, error codes and rate limits — all documented.