> ## 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.

# API Reference

> How to authenticate and call the Logo.dev APIs: base URLs, API keys, response codes, and rate limits.

Logo.dev splits into the image Logo API and a set of REST APIs on `api.logo.dev`. Which key you use depends on which one you call.

| API           | Base URL       | Returns      | Auth                       |
| ------------- | -------------- | ------------ | -------------------------- |
| **Logo API**  | `img.logo.dev` | A logo image | `pk_…` via `?token=`       |
| **REST APIs** | `api.logo.dev` | JSON         | `sk_…` via `Authorization` |

Get both keys from the [dashboard](https://www.logo.dev/dashboard). See [API keys](/platform/api-keys) for how they differ.

## REST APIs

Four JSON endpoints share the `api.logo.dev` base URL and your secret key:

| API                                          | What it returns                                                 | Plans                        |
| -------------------------------------------- | --------------------------------------------------------------- | ---------------------------- |
| [Search API](/brand-search/introduction)     | Company name to domain matches, each with a `logo_url`          | Free (Community) plan and up |
| [Describe API](/describe/introduction)       | Core company data: name, description, colors, socials, logo     | Any paid plan                |
| [Brand API](/brand/introduction)             | Full brand profile: the above plus brandmark and social banners | Pro and Enterprise           |
| [Transaction API](/transaction/introduction) | The merchant brand behind a card transaction string             | Early access                 |

The image Logo API also exposes `/ticker`, `/isin`, `/crypto`, and `/name` paths for looking up a logo image by those identifiers.

## Authentication

The Logo API takes a publishable key as a query parameter — safe to use in client-side code:

```html theme={null}
<img src="https://img.logo.dev/stripe.com?token=LOGO_DEV_PUBLISHABLE_KEY" />
```

The REST APIs take a secret key in the `Authorization` header — server-side only:

```bash theme={null}
curl --header "Authorization: Bearer LOGO_DEV_SECRET_KEY" "https://api.logo.dev/describe/stripe.com"
```

## Response codes

Logo.dev uses standard HTTP status codes. See [Errors](/platform/errors) for the full list and example payloads.

| Code  | Meaning                                                |
| ----- | ------------------------------------------------------ |
| `200` | Success                                                |
| `401` | Missing or invalid key                                 |
| `403` | Valid key, but your plan doesn't include this endpoint |
| `404` | No logo or brand data found                            |

## Rate limits

Limits are monthly, not per-second, and you're emailed before any enforcement kicks in. See [Rate limits](/platform/rate-limits) for the details.