> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brandfetch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Brand data for B2B Personalization

<Tip>
  If you have custom requirements, or any questions [contact
  us](https://brandfetch.com/developers/contact/sales).
</Tip>

[Brand API](https://brandfetch.com/developers/brand-api) provides programmatic access to any company's brand assets through a single API call. This includes their latest logos, color schemes, fonts, images, and other firmographic information.

Brand API works in real-time, if a brand is not part of our dataset, it will index the information live ensuring **global coverage** for businesses of all sizes, geography and industries.

## Implementation guide

For more details, refer to our [API Reference](/reference/brand-api).

<Steps>
  <Step title="Get your API key">
    You’ll need to create an account on our [Developer Portal](https://developers.brandfetch.com/register). Creating an account is quick and easy, and will give you access to your dashboard where you’ll find your API key.
  </Step>

  <Step title="Make your first API call">
    Implement or run the code below to make your first API request.

    <CodeGroup>
      ```curl curl theme={null}
      curl --request GET \
      --url https://api.brandfetch.io/v2/brands/{identifier} \
      --header 'Authorization: Bearer <token>'
      ```
    </CodeGroup>

    Authentication is done by passing your API key as a [Bearer Authentication](https://swagger.io/docs/specification/authentication/bearer-authentication/). The Brand API can be accessed through the following structure:

    <Note>
      To avoid potential naming collisions between identifier types (e.g., a Stock or ETF ticker that matches a domain), you can use explicit type routes: `/v2/brands/{type}/{identifier}` where `type` can be `domain`, `ticker`, `isin`, or `crypto`.
    </Note>
  </Step>

  <Step title="Test and deploy">
    All requests for the domain <b>brandfetch.com</b> are free and will not count towards your usage/quotas. You can make as many requests to the Brandfetch’s brand as you need while you iterate on and test your integration.

    Once you are ready to go live, simply replace <b>brandfetch.com</b> with the domain name, Stock/ETF ticker, ISIN, or Crypto symbol you want to look up.
  </Step>
</Steps>

## Query by domain, Stock/ETF ticker, ISIN, or Crypto symbol

The Brand API supports multiple identifier types to query brand data:

* **Domain:** `nike.com` (e.g., `https://api.brandfetch.io/v2/brands/nike.com`)
* **Stock or ETF ticker:** `NKE` (e.g., `https://api.brandfetch.io/v2/brands/NKE`)
* **ISIN:** `US6541061031` (e.g., `https://api.brandfetch.io/v2/brands/US6541061031`)
* **Crypto symbol:** `BTC`, `ETH` (e.g., `https://api.brandfetch.io/v2/brands/BTC`)

To avoid potential naming collisions between identifier types, you can use explicit type routes with the pattern `/v2/brands/{type}/{identifier}`:

<CodeGroup>
  ```curl Auto-detection theme={null}
  curl --request GET \
  --url https://api.brandfetch.io/v2/brands/nike.com \
  --header 'Authorization: Bearer <token>'
  ```

  ```curl Domain theme={null}
  curl --request GET \
  --url https://api.brandfetch.io/v2/brands/domain/nike.com \
  --header 'Authorization: Bearer <token>'
  ```

  ```curl Stock or ETF ticker theme={null}
  curl --request GET \
  --url https://api.brandfetch.io/v2/brands/ticker/NKE \
  --header 'Authorization: Bearer <token>'
  ```

  ```curl ISIN theme={null}
  curl --request GET \
  --url https://api.brandfetch.io/v2/brands/isin/US6541061031 \
  --header 'Authorization: Bearer <token>'
  ```

  ```curl Crypto symbol theme={null}
  curl --request GET \
  --url https://api.brandfetch.io/v2/brands/crypto/BTC \
  --header 'Authorization: Bearer <token>'
  ```
</CodeGroup>

### Auto-detection (legacy)

The original route `/v2/brands/{identifier}` still works and will auto-detect the identifier type. The detection order is: domain → Stock or ETF ticker → ISIN → Crypto symbol. However, **we recommend using explicit type routes** to prevent collisions and ensure accurate results.

If you only have company names, use the [Brand Search API](/brand-search-api/overview) to match brand names to the most likely URLs.

## API Reference

For more details, refer to our [API Reference](/reference/brand-api).