Skip to main content
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

1

Get your API key

You’ll need to create an account on our Developer Portal. Creating an account is quick and easy, and will give you access to your dashboard where you’ll find your API key.
2

Make your first API call

The Brand API supports multiple identifier types (domain, Stock or ETF ticker, ISIN, Crypto symbol). Authentication is done by passing your API key as a Bearer Authentication.
curl --request GET \
--url https://api.brandfetch.io/v2/brands/domain/nike.com \
--header 'Authorization: Bearer <token>'
The shorthand route /v2/brands/{identifier} (without a type prefix) is still supported and auto-detects the identifier type (in the order: domain → ticker → ISIN → crypto), but explicit type routes are recommended to avoid naming collisions.
If you only have company names, use the Brand Search API to match brand names to the most likely URLs.
3

Test and deploy

All requests for the domain brandfetch.com 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 brandfetch.com with the domain name, Stock/ETF ticker, ISIN, or Crypto symbol you want to look up.
If you have custom requirements, or any questions contact us.

​
Quotas and usage

When you sign up for a free developer account, you get 100 free requests. If you need to make more requests, please upgrade to a paid plan. When upgrading, you can confirm your quota by looking at the x-api-key-quota response header. To see your current month’s usage, look for the x-api-key-approximate-usage response header. We will also send you an email warning you upon reaching 80% of your quota. The API will return an HTTP status code 429 when the quota has been reached. In addition to a usage quota we also apply a request throughput limit to protect our service from abuse. By default, throughput is limited to a sustained 100 requests/second with some flexibility to accommodate bursts (30,000 requests / rolling 5 minute hard limit). You’ll receive an HTTP status code 429 when you exceed this limit. If your use-case requires higher throughput limits, contact us.

​
Overage billing

When you purchase a subscription plan, you are allotted a quota depending on the payment plan. When you make more API requests than your quota allows, rather than blocking requests which are over your quota, we apply overage billing. This means that you’ll never have any unexpected downtime. Requests over your quota are charged at an overage-fee rate. To set a spending limit, head to the Developer Dashboard and set a hard spending limit. Set this to $0 if you want to disable overage. Overage billing is not available on the free plan. To start using overage, please upgrade first to one of the paid plans.

​
API Reference

For more details, refer to our API Reference.