> ## 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. # Errors and status codes > Logo.dev API status codes. What 200, 202, 400, 401, 402, 403, 404, and 429 mean, plus how missing logos, credits, and rate limits are handled. The Logo.dev API uses standard HTTP status codes. The Logo API (`img.logo.dev`) returns an image on success; the REST APIs (`api.logo.dev`) return JSON. If a logo loads with a `200` but looks wrong (a white box, a monogram, or a blurry image), see [troubleshooting](/docs/platform/troubleshooting). **Branch on the status code, not the response body.** Error bodies are JSON with a short, human-readable message, under a `msg` key for auth, plan, and rate-limit errors, or an `err` key for bad requests and lookups. The key and the text can change, so don't parse them. ## Status codes | Status | Meaning | What to do | | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | `200` | Success. The Logo API returns an image, including a generated **monogram** when no logo exists (unless you set `fallback=404`). REST APIs return JSON. | Render the image or parse the JSON. | | `202` | Accepted. On the REST APIs, the domain isn't indexed yet and we've started fetching it. On the Logo API, the image is served while it revalidates in the background. | Retry the REST call in a few seconds. | | `400` | Bad request: an invalid domain, parameter, or query. | Fix the request. | | `401` | Missing or invalid key (or a restricted referrer). | Send a valid key. See [authentication](#authentication-errors-401). | | `402` | Out of credits: your Brand API balance is below the 5-credit request cost. | Buy credits, or upgrade your plan. See [out of credits](#out-of-credits-402). | | `403` | Your plan doesn't include this endpoint. | Upgrade, or use a different endpoint. | | `404` | Not found: the domain is known but has no data, or an image request used `fallback=404`. | Handle the missing result. | | `429` | You've hit your plan's request limit. | Slow down or upgrade. See [rate limits](/docs/platform/rate-limits). | | `500` | Server error. | Retry; contact [support](mailto:support@logo.dev) if it persists. | ## Authentication errors (`401`) The Logo API (`img.logo.dev`) takes a **publishable key** (`pk_…`) in the `token` query parameter. A request with no token returns `401`: ```bash theme={null} 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/"} ``` The REST APIs (`api.logo.dev`) take a **secret key** (`sk_…`) in the `Authorization` header. Missing it returns `401`: ```bash theme={null} curl -i "https://api.logo.dev/search?q=stripe" # HTTP/2 401 # {"msg":"missing api token"} ``` A publishable key (`pk_`) won't authenticate the REST APIs, and a secret key (`sk_`) won't authenticate the Logo API. See [API keys](/docs/platform/api-keys) for which key goes where. ## Plan errors Some endpoints require a paid plan: * **Describe API:** on a free account, returns `401` `{ "msg": "api not available for free accounts…" }`. The Brand API is not one of them. It's included on every plan and metered in credits, so a plan-related refusal there arrives as a [`402`](#out-of-credits-402), not a `403`. ## Not found vs. still indexing (`202`) For the Describe and Brand APIs, a domain we haven't indexed yet returns **`202`**, not `404`. We start fetching it, and you can retry shortly: ```bash theme={null} curl -i -H "Authorization: Bearer LOGO_DEV_SECRET_KEY" "https://api.logo.dev/describe/some-new-domain.example" # HTTP/2 202 # {"msg":"not found, looking up"} ``` A `404` `{ "err": "not found" }` means the domain is known but has no data (or is blocked). Each call counts as one request, including the `202` and any retries. Back off a few seconds between tries so you don't spend extra requests on repeated `202`s. See [rate limits](/docs/platform/rate-limits). ## Missing logos By default, an image 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`: ```html Default: monogram fallback (200) theme={null} ``` ```html Opt into 404 for missing logos theme={null} ``` See [fallback images](/docs/logo-images/introduction#fallback-images) for the full pattern. ## Out of credits (`402`) The Brand API is prepaid: each request uses 5 credits. When your balance drops below that cost, requests return `402` `{ "msg": "…" }` until your plan's monthly credit grant renews or you top up. This is a different condition from a `429`: it's about your credit balance, not a request limit. What to do next depends on your plan. On Pro, Enterprise, or a custom contract, buy credits on the [billing page](https://www.logo.dev/dashboard/billing). On every other plan, upgrade to Pro: it raises the monthly grant from 500 credits to 15,000 and unlocks credit purchases. See [credits](/docs/platform/rate-limits#credits). ## Rate limits (`429`) If you exceed your plan's request limit, the API returns `429` `{ "msg": "…" }`. This applies to the **monthly request pool** on the free tier. On paid plans, pool enforcement is soft. We email you before acting, so you generally won't hit a `429` unexpectedly. Running out of the Brand API's prepaid credits returns a [`402`](#out-of-credits-402) instead. See [rate limits](/docs/platform/rate-limits) for details. ## Response headers Logo.dev returns no `Retry-After`, `X-RateLimit-*`, or quota headers on any endpoint. There's nothing to read for a server-suggested backoff or remaining requests, so set your own policy: * **`202` (still indexing):** there's no fixed retry count to read from the response. [Back off a few seconds between tries](#not-found-vs-still-indexing-202), and cap it at a handful of attempts rather than looping indefinitely if a domain never resolves. * **`402` (out of credits):** retrying doesn't help; requests resume once you top up on the [billing page](https://www.logo.dev/dashboard/billing) or your monthly credits renew. * **`429` (over limit):** see [rate limits](/docs/platform/rate-limits) for how enforcement differs by plan. Track remaining requests in your [dashboard](https://www.logo.dev/dashboard), the source of truth for usage. ## FAQs Your request is missing a token or using the wrong key. The Logo API needs a publishable key (`pk_`) as `?token=`; the REST APIs need a secret key (`sk_`) as `Authorization: Bearer`. Check the [API keys guide](/docs/platform/api-keys). The domain isn't in our index yet. The `202` kicks off a fetch. Retry the request in a few seconds and it'll resolve once indexed. 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. When you exceed your plan's monthly request pool on the free tier. On paid plans, pool limits are soft and you're emailed before any enforcement. The Brand API's credits are metered separately from the request pool: running out of credits returns a [`402`](#out-of-credits-402) rather than a pool `429`. See [rate limits](/docs/platform/rate-limits). No. Branch on the HTTP status code. The JSON body is for debugging. The key (`msg` or `err`) and the wording can change.