Errors and status codes

Logo.dev uses standard HTTP status codes. Branch on the status code, and on the error.code of a Logo.dev API error. Message text is for people and can change, so don’t parse it. If a logo loads with a 200 but looks wrong, such as a white box, a monogram, or a blurry image, see troubleshooting.

Logo.dev CDN status codes

img.logo.dev returns an image on success. An error body is a short JSON object with a msg or an err key, and a docs_url that links the relevant docs page.

Status	Meaning	What to do
`200`	The logo. For a lookup with no logo, a generated monogram, unless you set `fallback=404`.	Show the image.
`202`	The first request for a domain Logo.dev is still fetching. The body is an image, cached for 5 minutes.	Show the image. Later requests return the logo.
`400`	A malformed ticker, crypto symbol, exchange, or index, or an invalid parameter on `/isin` or `/name`	Fix the request.
`401`	A missing, invalid, or disabled publishable key, or a request from a domain your key does not allow	See authentication errors.
`403`	The account is suspended, personal keys are off because you belong to a team, or a Community account is paused for a few hours for abusive traffic	Contact support, or use your team’s keys.
`404`	No logo, with `fallback=404` set. Also an invalid parameter value, such as `format=gif`, on the domain, ticker, crypto, exchange, and index routes.	Handle the missing logo, or fix the parameter.
`429`	Over the Community plan’s monthly or per-minute limit	On a per-minute limit, wait the seconds in `Retry-After`. See Logo.dev CDN limits.
`500`	Logo.dev could not fetch the logo	Retry.

Logo.dev API status codes

A failed request to api.logo.dev returns an error object and a docs_url. target names the parameter at fault when there is exactly one.

{
  "error": {
    "code": "invalid_request",
    "message": "q is required",
    "target": "q"
  },
  "docs_url": "https://www.logo.dev/docs/platform/errors"
}

Code	Status	Meaning
`invalid_request`	`400`	A parameter is missing or malformed
`insufficient_credits`	`402`	The account is out of API credits. See out of API credits.
`forbidden`	`403`	Your account or role cannot do this. The identifier type is not enabled yet (such as `merchant`), webhooks are not turned on for the account, or your role cannot change them. Not billed.
`limit_exceeded`	`409`	Your account is at its plan’s limit on webhook endpoints or brand subscriptions. Delete one, or upgrade. See plan limits.
`resource_missing`	`404`	The id matches nothing
`rate_limited`	`429`	Over a per-minute limit, or over the limit on open lookups. Lookups and search have separate per-minute limits. See Logo.dev API rate limits.
`internal`	`500`	Retry. If it persists, contact support with the `Request-Id` header.

A lookup that finds no brand is not an error. It returns 404 inside the normal envelope, with data.status set to not_found, and it is free. Every API response carries a Request-Id header. Include it when you contact support. See response headers for the rest.

Authentication errors (`401`)

Authentication runs before the route, so an authentication error has a msg field instead of an error object, on both hosts. That covers every 401, and the 403 for a suspended account or for personal keys turned off by team membership.

curl -i "https://img.logo.dev/stripe.com"
# HTTP/2 401
# {"docs_url":"https://www.logo.dev/docs/platform/api-keys","msg":"invalid api token. get an api token by creating an account at https://www.logo.dev/"}

A 401 has one of these causes:

The key is missing or does not exist.
The key is the wrong type for the host. See API keys.
The key is disabled.
On the CDN, domain restrictions block the request. The message starts with invalid referrer.

Not found vs. still indexing (`202`)

An API lookup of a brand that Logo.dev has not indexed yet returns 202, not 404. Logo.dev starts to fetch the brand, which is usually ready within a minute. The response has a Retry-After: 30 header and a metadata.pending object:

{
  "data": { "object": "brand", "status": "not_indexed" },
  "metadata": {
    "request_id": "request_01k6z8m2a4b5c6d7e8f9g0h1j2",
    "resolution": { "type": "domain", "value": "example.com", "method": "direct", "context": {} },
    "pending": {
      "reason": "indexing",
      "message": "This brand is being indexed for the first time and is usually ready within a minute. Retry the same request after 30 seconds; retries are not billed.",
      "retry_after_seconds": 30,
      "expires_in_seconds": 300,
      "webhook": true,
      "doc_url": "https://www.logo.dev/docs/platform/errors#not-found-vs-still-indexing-202"
    }
  }
}

reason is indexing during a brand’s first crawl. The value resolving is reserved for a lookup that is still matching the identifier to a brand.
Retry the same request after retry_after_seconds. Retries are not billed. Stop after expires_in_seconds, which is 5 minutes.
If webhook is true, a brand.indexed event tells you when the lookup settles, so you can stop polling.

A 404 with data.status set to not_found means no brand matches the identifier.

Missing logos

A CDN lookup with no logo returns 200 with a generated monogram, so the image never breaks. With fallback=404, it returns 404 instead, and you show your own image. See fallback images for the pattern.

Out of API credits (`402`)

An API request returns 402 with the code insufficient_credits when your API credit balance is below the request’s cost. Retrying does not help. Requests work again after you add API credits or your monthly grant renews. See API credits for how to add them.

Get started

CDN

API

Platform

Switch to Logo.dev

Integrations

Get your logo seen

Comparisons

Support

Errors and status codes

Logo.dev CDN status codes

Logo.dev API status codes

Authentication errors (`401`)

Not found vs. still indexing (`202`)

Missing logos

Out of API credits (`402`)

​Logo.dev CDN status codes

​Logo.dev API status codes

​Authentication errors (401)

​Not found vs. still indexing (202)

​Missing logos

​Out of API credits (402)

Logo.dev CDN status codes

Logo.dev API status codes

Authentication errors (`401`)

Not found vs. still indexing (`202`)

Missing logos

Out of API credits (`402`)