- Identity: tagline, mission, description, and tags.
- Positioning: value proposition, target audience segments, and products & services.
- Brand: a summary of the brand’s voice and visual style, with descriptive attributes.
Implementation guide
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.
Make your first API call
Implement or run the code below to make your first API request.Authentication is done by passing your API key as a Bearer Authentication, the same way as the Brand API.
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 Brandfetch’s own 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 you want to look up.
Query by domain
The Brand Context API is queried by domain name:Content negotiation
The Brand Context API supports content negotiation. Use theAccept request header to choose the format of the response:
application/json(default) — returns the structured JSON object described below.text/markdown— returns the brand context as a Markdown document, ready to drop directly into an LLM prompt or a Markdown-aware surface.
Response shape
When requestingtext/markdown, the response is a Markdown document covering the same information. When requesting application/json, the response is grouped into a few top-level objects:
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 thex-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.