Skip to main content
What you can store depends on which API the data came from. Logo API images are meant to be hotlinked, never stored. Brand API responses and their images can be kept for up to 30 days before you refresh them. These rules come from the Brandfetch terms of service. If you need to keep data longer or host logo files yourself, talk to sales about a custom agreement. A Logo API URL is meant to sit in an <img> tag, with the image served straight from Brandfetch’s CDN. When a brand updates its logo, the same URL returns the new one, so there’s no copy for you to keep in sync. For the same reason, you can’t download, proxy, or re-host Logo API images. A request that looks programmatic, like a fetch from your server or a script, is redirected with automated_traffic, even when it carries a valid client ID. The usage guidelines have the details. If your product can’t hotlink, whether for privacy or compliance reasons or because it works offline, the Enterprise plan includes self-hosted logos with custom licensing terms, delivered as a bulk file and kept current with webhooks.

Brand API: cache for up to 30 days

You can store a Brand API response, along with the logos and images it links to, for up to 30 days from the day you fetched it. Before the 30 days are up, call the Brand API again for that brand to refresh your copy. Anything older than 30 days that you haven’t refreshed has to be deleted. Caching also saves credits. A brand served from your own cache doesn’t use one, and only the refresh counts, as a normal Brand API call.
This check only removes a brand when someone asks for it again, so a brand that is never requested after its first fetch would stay in your database. Set an expiry on each record or run a scheduled cleanup that deletes anything fetched more than 30 days ago.

Keep the cache fresh

  • Key the cache by domain. One call then covers every user who signs up from the same company.
  • Record when you fetched each brand. Refetch a brand before you use it once it’s older than 30 days, or refresh old entries on a schedule.
  • Refresh when a brand changes. Subscribe to webhooks for the brands you store. brand.updated fires when a brand’s data changes, and brand.rebranded fires when it gets a new logo. Webhooks are available on every paid plan.
  • Use image URLs exactly as returned. Their t parameter changes whenever the image does, so a new URL always means a new image. See shortcut fields.

What cached data can be used for

Cached data is for use inside your own product, within your plan. You need an agreement to resell, sublicense, or redistribute it, including in your own API responses, and to use it to train AI or machine learning models. When your subscription ends, delete everything you cached. The terms license Brandfetch’s data, not the logos themselves, which belong to their owners. See logo fair use.

A user’s own logo at onboarding

There’s one exception to the 30-day rule. When a user signs up and you fetch their own company with the Brand API, you can save that logo to their account. It becomes their asset, just like a file they uploaded themselves. See populate onboarding. This covers only the user’s own brand. Other companies’ brands, like those in a customer list or a directory, still follow the 30-day rule.

Brand Search API: don’t store results

The Brand Search API is built for autocomplete. Show its results while the user types, but don’t store them. Hotlink the icon URLs, which expire after 24 hours. Once the user picks a brand, keep its domain. Use it with the Logo API to show the logo, or with the Brand API to get the full brand.

Pick by use case

FAQ

No. Logo API images have to be hotlinked from the CDN, and server-side or scripted requests are redirected with automated_traffic. If you need logo files, get them through the Brand API and follow the 30-day rule, or ask sales about self-hosted assets.
Up to 30 days from the day you fetched it. Refresh it with a new Brand API call before then, or delete it.
No. Only calls to the Brand API use credits, so each refresh uses one.
Only with a custom agreement. Enterprise plans include self-hosted assets and custom licensing terms, so talk to sales if you need them.