Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.logo.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

The Logo.dev API uses standard HTTP status codes. The image CDN (img.logo.dev) returns an image on success; the REST APIs (api.logo.dev) return JSON. Error responses are always JSON with a msg field.

​
Image CDN (img.logo.dev)

StatusMeaningWhat to do
200Logo returned. Also returned with a generated monogram when no logo exists for a valid request (unless you set fallback=404).Nothing — render the image.
401Missing or invalid token.Add a valid publishable key as ?token=.
404No logo found and you requested fallback=404.Handle the missing logo in your code.
401 — no or invalid token
{ "msg": "invalid api token" }
A request without a token returns 401: 
curl -i "https://img.logo.dev/stripe.com"
# HTTP/2 401
# {"msg":"invalid api token. get an api token by creating an account at https://www.logo.dev/"}

​
REST APIs (api.logo.dev)

The Brand Search and Describe APIs authenticate with a secret key in the Authorization header.
StatusMeaningWhat to do
200Success. Returns JSON.Parse the response.
401Missing or invalid secret key.Send Authorization: Bearer LOGO_DEV_SECRET_KEY.
401 — missing secret key
{ "msg": "missing api token" }
REST endpoints require a secret key (sk_) in the Authorization header — a publishable key (pk_) passed as a token query parameter will not authenticate. The Describe API also requires a paid plan.

​
Handling missing logos

By default, a request for a domain with no logo returns 200 with a generated monogram, so images never break in your UI. To detect and handle missing logos yourself, request fallback=404:
Default — monogram fallback (200)
<img src="https://img.logo.dev/unknown-domain.example?token=LOGO_DEV_PUBLISHABLE_KEY" />
Opt into 404 for missing logos
<img
  src="https://img.logo.dev/unknown-domain.example?token=LOGO_DEV_PUBLISHABLE_KEY&fallback=404"
  onerror="this.src='/images/default-logo.png'"
/>
See fallback images for the full pattern.

​
Rate limits

Logo.dev enforces monthly request counts, not per-second or per-minute bursts — so there is no 429 response in normal use. You’re emailed before any enforcement, and service continues while you sort it out. If logos stop loading, it’s almost always an authentication or implementation issue, not a rate limit. See rate limits for details.

​
FAQs

Your request is missing a token or using the wrong key. The image CDN needs a publishable key as ?token=; the REST APIs need a secret key as Authorization: Bearer. Check the API keys guide.
By design. Missing logos return a 200 monogram so your UI never shows a broken image. Add fallback=404 if you’d rather handle missing logos yourself.
No. Limits are monthly, and you’re notified by email before any action — there are no burst limits. See rate limits.
Almost certainly not. Check your token and implementation first; we don’t cut off service without emailing you.