Skip to main content
The Brand API turns a company identifier into structured brand data. Send a domain, website URL, email address, stock ticker, ISIN, or crypto symbol, and get back the company’s logos, colors, fonts, images, description, and company data in one JSON response. Brands that are not indexed yet are crawled live during the request, so coverage is not limited to a fixed list. See real-time indexing.

Make your first request

Create a free account in the developer dashboard to get an API key, then call the API from your server:
Requests for brandfetch.com are free, so you can build your integration without spending quota. Swap in any other identifier when you are ready.
Building an agent with no account? It can pay per request with x402 or MPP instead of using an API key.

What it returns

Here is the response for brandfetch.com, shortened:
Image URLs carry a client ID signed for your key. Use them exactly as returned, and they do not count towards your quota. The API reference documents every field.

Shortcut fields

Most integrations show one image of each kind, so every response carries four shortcut fields: logo, symbol, icon, and banner. Each one holds the address of the best match from logos or images, or null when the brand has no image of that kind. Put the address straight into an <img> tag. Logos and images explains how each best match is picked, the image sizes, and how to cache them.

Go further

Batch lookups

Look up to 100 brands in one request.

Real-time indexing

Prefetch brands ahead of time, or skip the crawl with cachedOnly.

Color palette

Color roles, themes, contrast pairs, and CSS tokens.

Typography

Font roles, fallbacks, licenses, and the type scale.

Webhooks

Get notified when a brand you follow changes.

Quotas and usage

The Brand API, Brand Context API, and Transaction API share one quota, counted in brand fetches. The free plan includes 100. See limits and billing for quotas, throughput, and overage.

Errors

When the Brand API refuses a request, the response says why in two places. The x-bf-error header carries one code. The JSON body repeats that code as error, beside the message you have always received and a docs link to this table. Branch on the code, not on the message text.
A 402 is the exception, whether no credential was sent or a payment was not accepted: its body is the payment protocols’ own, so only the header names the refusal (payment_required). API Gateway answers a few requests itself, for example a throughput limit. Those responses carry no x-bf-error header. The Transaction API uses most of the codes below and adds two of its own, body_invalid and transaction_unmatched, listed in Transaction API errors.

The request

The credential

The brand

Every 404 below uses one API credit: you asked us to look, and we looked. A pay-per-request 404 is settled too, except crawl_queued: that payment is not charged, the body says so in a payment object, and the same payment can be presented again for the retry. The code tells you whether asking again can help.

Our side

The errors overview explains how codes work across every Brandfetch API.