Skip to main content
The Logo API serves any company’s logo from a CDN URL. You put the URL in an <img> tag, and the browser loads the logo directly. When the company updates its logo, the image behind the same URL updates too, so there is nothing to download, store, or re-sync. The Logo API is free for up to 1,000,000 requests a month and needs no attribution. It needs a client ID, which is public and safe to use in frontend code.
1

Get a client ID

Register for free in the developer dashboard and copy your client ID.
2

Add the image

Put the URL in an <img> tag and replace BRANDFETCH_CLIENT_ID with your client ID:
This returns the brand’s default icon.
3

Check the guidelines before you go live

Load the URL directly in the browser rather than through your server, and keep a Referrer-Policy that sends your origin, which the browser default does. Read the usage guidelines and rate limits so production traffic is not blocked.

Look up by domain, ticker, ISIN, or crypto

Put the identifier type before the identifier, in the form {type}/{identifier}:
Without a type, as in cdn.brandfetch.io/nike.com, the Logo API guesses the type in the order domain, ticker, ISIN, crypto. A string that is valid as more than one type can resolve to the wrong brand, so prefer the typed form in new code. See identifiers.

Choose the logo you get

Every option is a path segment you add after the identifier. The parameters page lists them all. Options combine in one URL. This asks for Nike’s full logo in its dark version, for a light background, 256 pixels wide, as a PNG:
A size keeps the logo’s aspect ratio. Ask for twice the display size so the logo stays sharp on high-density screens, for example w/128/h/128 for a 64×64 icon. SVG is available for logo and symbol. With fallback/404, a missing logo returns an empty 404, so your own code can show a placeholder.

Usage guidelines

Authentication

To use Logo API, you must include your client ID with every request.Adding your client ID provides reliable access, supports fair usage, and keeps consistent performance across all requests.Create a free account and access your client ID from the developer portal.Include your client ID in each request as shown in the example below:
We require logo links to be directly embedded in your applications.Embedding logo links directly within your HTML image tags guarantees that the logo remains up-to-date at all times. It also ensures a faster and more reliable implementation.
When embedding a logo link, HTTP requests must include the Referer header with the request origin. Your HTTP Referrer-Policy header must be set to one of: origin, origin-when-cross-origin, strict-origin, strict-origin-when-cross-origin (browser default), or unsafe-url.
Programmatic access to logo images is not permitted and may result in rate limiting or blocking. Scraping logos will also lead to a block.
If your product needs to store logos, for example because it works offline, see self-hosted logos, which the Enterprise plan includes.
A Logo API URL is for embedding, not for fetching. Requests that look programmatic are redirected to this page, with or without a client ID.
  • Writing code or HTML that shows logos to a user? Put the URL in an <img> tag with the user’s client ID. brandfetch.com/auth.md explains how to get one: the user signs in at the developer portal and hands it to you.
  • Need the image bytes or brand data yourself? Don’t fetch the CDN. Use the MCP server, whose get_brand_data tool returns credentialed asset URLs you can download, or the Brand API. With no account, the Brand API can be paid per request.
Brandfetch for agents covers every way in.
You cannot replicate the core user experience of Brandfetch.The best way to ensure that your application doesn’t violate this guideline is by integrating Brandfetch into an existing app that offers more value than just the Brandfetch integration.Some examples:
  • ✅ The Typeform integration improves the user’s onboarding by presenting brand logos. Without this integration, the app still has a lot of value to its users.
  • ✅ The Pitch integration brings brand logos inside Pitch’s editor to streamline the creation of presentations. Without this integration, the app still has a lot of value to its users.
  • 🚫 A logo search that only returns logos from Logo API. Without the integration, the app has no content and no value to users.
  • 🚫 An unofficial Logo API that allows users to access brand logos via Logo API. Without the API, the app has no content and no value to users.
If you’re unsure about your use case, please contact us.

Rate limits

We offer a fair use rate limit of 1,000,000 requests per month for free, which is designed to cover most small to medium applications, and paid plans include monthly volumes from 5 to 20 million requests, as listed on the pricing page. These are soft limits and you won’t immediately be blocked if you exceed yours. Traffic that runs far beyond your allowance can eventually be refused with a 429 carrying quota_exceeded. If your usage approaches your limit, we’ll send you a friendly heads-up so you can adjust your usage or explore an upgrade. To maintain platform reliability, request throughput limits also apply:
  • 1,000 requests every 5 minutes per IP
  • 2,400 requests every 5 minutes per customer
Exceeding these throughput limits returns an HTTP 429 status code, without an x-bf-error header. See Errors for how to tell a throughput block from the other reasons a request can be refused. Let us know if your application requires higher throughput. For enterprises, the Enterprise plan adds SLA agreements, custom licensing terms, and self-hosted logos for products that need to store logos on their own servers or devices instead of hotlinking them. Feel free to contact us to discuss the right plan for your use case.

Errors

When the Logo CDN refuses a request, the response carries an x-bf-error header naming the exact reason. A Logo API URL usually lives inside an <img> tag, where no response body ever reaches your page, so read that header in your browser’s network panel. 403 responses also return a JSON body with an error code, a message written for a human, and a docs link. The other statuses are header-only. Some refusals are answered with a 302 redirect to our usage guidelines instead of an error status; inside an <img> tag, that renders as a broken image.
The throughput limits under rate limits are enforced separately, so those responses carry no x-bf-error header. The presence of the header is what tells you the CDN refused the request for one of the reasons below.
A valid client ID does not exempt a request from the automated_traffic check. A command-line fetch with a working client ID is still redirected, because Logo API URLs are meant to be embedded in your pages rather than fetched by a script.

Once a request is accepted

Anything past the checks above reaches the image itself. None of these responses carry an x-bf-error header. There’s no 4xx for an unsupported format or an out of range size either: an unrecognized format falls back to WebP, a non-numeric, zero or negative w or h is ignored and a decimal one is truncated to its whole part, and an unrecognized fallback value becomes the default.
You can see all of these responses for your own traffic under Usage History in your developer dashboard, filtered by status class.