Skip to main content
Every Brandfetch request starts with something that points at a company: a domain, a stock ticker, a name someone typed, or a line on a bank statement. Brandfetch resolves that input to one brand and returns its data.

Which API accepts what

The table shows which identifiers the Logo API, Brand API, and Brand Context API accept. Two other inputs go through their own APIs instead. A company name such as Nike goes to the Brand Search API, which finds its domain so you can use the domain everywhere else, and a card or bank transaction label such as NIKE STORE 0423 NEW YORK goes to the Transaction API, which returns the merchant’s brand.

Domain

The domain is the most reliable identifier. A company has one registrable domain, and Brandfetch can index any live domain, including companies nobody has asked about before. See real-time indexing.

Website URL and email address

A URL resolves to the registrable domain of its host, and an email address resolves to the registrable domain of the part after the @. https://www.brandfetch.com/developers/pricing and john@example.brandfetch.com both return the same brand as brandfetch.com. Brandfetch does not store the URL or the address. Your request logs show only the resolved domain. URLs and email addresses work on the shorthand route (/v2/brands/{identifier}), not on typed routes.

Brand ID

Every brand has a Brand ID such as id_0dwKPKT. The Brand API returns it as id. Store it next to your own records so you can fetch the same brand later without resolving the domain again.

Ticker, ISIN, and crypto symbol

Financial identifiers resolve to the company or asset behind them. Tickers cover stocks and ETFs, ISINs cover securities, and crypto symbols cover tokens such as BTC and ETH.

Typed routes and auto-detection

The Logo API and Brand API accept a typed route, {type}/{identifier}, which states what the identifier is:
Without a type, the API guesses in this order: domain, ticker, ISIN, crypto. A string that is valid as more than one type can resolve to the wrong brand, so use typed routes in production.