Skip to main content

​
Brand API

​
Overview

​
Brand Data API for B2B Personalization

BrandsAPI gives developers programmatic access to company brand assets through a simple API request. With BrandsAPI, you can retrieve accurate brand data such as logos, colors, fonts, images, company metadata, and other brand-related information. It helps B2B platforms personalize user experiences, enrich company profiles, and display consistent brand identities across applications. BrandsAPI is built to provide reliable brand data for companies of different sizes, industries, and regions. If a brand is missing or incomplete, the system can help keep brand information fresh and useful for real-world product use cases.

​
Implementation Guide

For complete technical details, refer to the API Reference.

​
1. Get Your API Key

To start using BrandsAPI, create an account on the developer dashboard. After signing up, you can access your dashboard and generate your API key. This key is required to authenticate requests and securely access the Brand API.

​
2. Make Your First API Call

Use your API key to send your first request to the BrandsAPI endpoint. 
curl --request GET \
  --url https://api.brandsapi.com/v1/brands/{identifier} \
  --header 'Authorization: Bearer <token>'
Authentication is handled through Bearer Authentication. Pass your API key in the request header to access brand data. BrandsAPI can return brand information using a supported company identifier, such as a domain name, ticker, ISIN, or crypto symbol. To avoid confusion between different identifier types, you can use explicit routes:
  • /v1/brands/domain/{identifier}
  • /v1/brands/ticker/{identifier}
  • /v1/brands/isin/{identifier}
  • /v1/brands/crypto/{identifier}
Where {type} can be:
  • domain
  • ticker
  • isin
  • crypto

​
3. Test and Deploy

Before going live, test your integration using a sample brand request. Once your implementation is working correctly, replace the sample identifier with the company domain, stock or ETF ticker, ISIN, or crypto symbol you want to search. This allows you to move from testing to production without changing your integration flow.

​
Query by Domain, Stock/ETF Ticker, ISIN, or Crypto Symbol

BrandsAPI supports multiple identifier types, making it easier to fetch brand data from different business, finance, and Web3 data sources.

​
Domain

Use a company domain to retrieve brand assets. nike.com Example: 
curl --request GET \
  --url https://api.brandsapi.com/v1/brands/domain/nike.com \
  --header 'Authorization: Bearer <token>'

​
Stock or ETF Ticker

Use a public company stock or ETF ticker to fetch brand information. NKE Example: 
curl --request GET \
  --url https://api.brandsapi.com/v1/brands/ticker/NKE \
  --header 'Authorization: Bearer <token>'

​
ISIN

Use an International Securities Identification Number to identify a company or financial instrument. US6541061031 Example: 
curl --request GET \
  --url https://api.brandsapi.com/v1/brands/isin/US6541061031 \
  --header 'Authorization: Bearer <token>'

​
Crypto Symbol

Use a crypto symbol to retrieve brand data for supported crypto assets. BTC Example: 
curl --request GET \
  --url https://api.brandsapi.com/v1/brands/crypto/BTC \
  --header 'Authorization: Bearer <token>'

​
Auto-Detection

BrandsAPI can also detect the identifier type automatically when using a general brand lookup route. 
curl --request GET \
  --url https://api.brandsapi.com/v1/brands/{identifier} \
  --header 'Authorization: Bearer <token>'
Auto-detection can be useful when you want a simple integration. However, explicit type routes are recommended when accuracy is important, especially when identifiers may overlap. For example, a ticker symbol may match a domain name, or a crypto symbol may conflict with another identifier. Using explicit routes helps prevent naming collisions and improves lookup accuracy. If you only have a company name, use the Brand Search API to find the most relevant brand or domain before requesting complete brand data. This is useful when users enter company names instead of domains, tickers, ISINs, or crypto symbols.

​
API Reference

For endpoint details, request parameters, authentication rules, and response examples, refer to the API Reference.