Usage guidelines

Usage guidelines for the Logo API

Usage guidelines for the Logo API.

Logo API is free to use, and attribution is not required.

Authentication

To use Logo API, you must include your Client ID with every request. Adding your Client ID helps provide reliable access, supports fair usage, and keeps performance consistent across all logo requests. Create a free account and access your Client ID from the Developer Portal. Include your Client ID in each request as shown below:

<img
  src="https://cdn.brandapi.io/:domain?c=YOUR_CLIENT_ID"
  alt="Company logo from Logo API"
/>

Hotlinking

Logo API links must be embedded directly inside your application or website. Embedding logo links directly in your HTML image tags keeps logos up to date and makes implementation faster and more reliable.

Example:

<img
  src="https://cdn.brandapi.io/nike.com?c=YOUR_CLIENT_ID"
  alt="Nike logo from Logo API"
/>

When embedding a logo link, HTTP requests must include the Referer header with the request origin. Your HTTP Referrer-Policy header must be set to one of the following values:

• origin
• origin-when-cross-origin
• strict-origin
• strict-origin-when-cross-origin
• unsafe-url

Programmatic access to logo images is not permitted and may result in rate limiting or blocking. Scraping logos from Logo API is also not allowed and may lead to access being blocked. If your use case requires caching, contact us at [e-mail] for a custom setup.

Replicating Brand API

You cannot use Logo API to replicate the core experience of Brand API. Logo API should be integrated into an existing product, platform, or workflow that provides additional value beyond logo retrieval. The best way to follow this guideline is to use Logo API as a supporting feature inside a larger application.

Allowed Use Cases

• ✅ A form builder uses Logo API to show company logos during customer onboarding.
• ✅ A presentation tool uses Logo API to help users add brand logos inside slide decks.
• ✅ A CRM uses Logo API to display company logos inside customer profiles.
• ✅ A dashboard uses Logo API to make company lists easier to scan and recognize.

In these cases, the application still provides value even without the Logo API integration.

Not Allowed Use Cases

• 🚫 A logo search website that only returns logos from Logo API.
• 🚫 An unofficial logo API built on top of Logo API.
• 🚫 A product that has no meaningful functionality beyond accessing or displaying logos from Logo API.
• 🚫 A scraping tool that collects, stores, or redistributes logos from Logo API.

In these cases, the product depends entirely on Logo API and may violate the usage guidelines.

Questions About Your Use Case

If you are unsure whether your use case follows the Logo API usage guidelines, contact us at: [e-mail]