Brand API: Company Brand Assets by Domain

The Brand API returns a domain’s full brand profile in a single JSON response: logo, brandmark, social banner images, brand colors, description, and social profiles. It takes a secret key and is included on every plan: each plan comes with monthly credits, and a request uses 5 of them. Use cases, plan availability, and a live demo are on the Brand API product page.

curl --header "Authorization: Bearer LOGO_DEV_SECRET_KEY" "https://api.logo.dev/brand/sweetgreen.com"

The response is a single JSON object. The brandmark field is a wide lockup of the logo and wordmark, and social_banners holds the profile’s banner images:

{
  "name": "sweetgreen",
  "domain": "sweetgreen.com",
  "description": "Simple, seasonal, healthy salads and grain bowls made in-house from scratch.",
  "indexed_at": "2025-03-10T11:36:23Z",
  "socials": {
    "facebook": "http://facebook.com/sweetgreen",
    "instagram": "https://www.instagram.com/sweetgreen/",
    "twitter": "https://x.com/sweetgreen"
  },
  "logo": "https://img.logo.dev/sweetgreen.com?token=LOGO_DEV_PUBLISHABLE_KEY",
  "brandmark": "https://img.logo.dev/brand/sweetgreen.com/wjn3jfH379v17a0ULgzhxiD1djDnhc8rcAqXHIzWApPe16INmZ3L?token=LOGO_DEV_PUBLISHABLE_KEY",
  "social_banners": [
    "https://img.logo.dev/brand/sweetgreen.com/bvqSYvYpNqZxuWGHiuruKU1_GWDHHd-GJtEnZwLObs9P4_PngWWC?token=LOGO_DEV_PUBLISHABLE_KEY"
  ],
  "logo_blurhash": "UJPanPxr?Vj[oxazj@od_FWDDoodxrodagWD",
  "colors": [
    { "hex": "#e4ff55", "r": 228, "g": 255, "b": 85 },
    { "hex": "#0a4b2b", "r": 10, "g": 75, "b": 43 }
  ],
  "is_profane": false
}

A domain that isn’t in the index yet returns 202 while Logo.dev fetches it. Retry in a few seconds. See errors and status codes. Brand responses can take longer than a typical API call, because Logo.dev may prepare the profile’s assets at request time. Set your HTTP client timeout to at least 15 seconds, ideally 30. On serverless platforms, default function timeouts like Vercel’s maxDuration can sit below 15 seconds and end the request before the API responds. See the full request and response in the Get a brand profile reference.

What a brand API does

You already hold domains. They arrive in work emails at signup, sit on CRM records, and hide inside payment descriptors. A brand API resolves a domain into the public identity behind it: the company’s name, what it does, how it looks, and where it lives on social platforms. The input is one GET request with a domain. The output is one JSON object your code renders directly, with no crawler to run and no image files to host.

What’s in the response

Profiles carry these fields:

Field	What it holds
`name`	The canonical company name.
`domain`	The domain the profile describes.
`description`	A short summary of what the company does.
`indexed_at`	When Logo.dev last verified the profile.
`socials`	Profile links for the platforms the company uses, out of the 13 Logo.dev detects.
`social_banners`	Banner images from those social profiles, served from the Logo.dev CDN. The list is `null` when the profile has none.
`logo`	A ready-to-embed URL for the square logo.
`brandmark`	A URL for the wide logo lockup: the icon and wordmark together for most brands, the wordmark alone for pure-type brands. The key is omitted when no brandmark has been selected yet.
`logo_blurhash`	A compact string that renders a blurred placeholder while the logo loads.
`colors`	The brand’s dominant colors in hex and RGB, strongest first.
`is_profane`	Whether the brand tripped profanity detection, so you can filter what you show.

The logo and brandmark URLs point at img.logo.dev, the same CDN behind the Logo API. The image you render and the data you fetch come from one index, so they stay in sync. brandmark and social_banners URLs are scoped to your account and expire after 24 hours, so render them from a fresh response rather than storing them. Check both before you render: brandmark can be absent, social_banners can be null, and a URL with no path after the hostname means no asset was selected. Fall back to logo in each of those cases.

One request instead of a pipeline

The build-it-yourself version of this data is a pipeline: a crawler to fetch each site, parsers to pull the name and description, image processing to extract logos and colors, and a re-crawl schedule to catch rebrands. Each stage breaks on its own schedule, and stale assets look like bugs to your users. The Brand API replaces that with a single request at render time. Logo.dev crawls continuously, so indexed_at tells you when a profile was last verified rather than when you last found time to re-scrape.

Authentication and plans

The Brand API takes your secret key (sk_...) as a bearer token. Call it from your server: the secret key reads brand data for any domain, so keep it out of client code and git. Every plan includes the Brand API, with a monthly credit grant that renews on your billing date. Community and Startup get 500 credits, and Pro gets 15,000. A request uses 5 credits, so that’s 100 calls a month on Community and Startup and 3,000 on Pro. Enterprise grants are set in your contract. Past your grant, requests draw on prepaid credits at 1¢ each. Run out of both and requests return 402 until you top up or the next grant lands. On Pro, Enterprise, or a custom contract you can buy credits on the billing page. Every other plan upgrades to Pro first. See credits for the full model and out of credits for the response shape.

Next steps

Get a brand profile

Full request, parameters, and response reference.

Migrate from Brandfetch

Map each Brandfetch Brand API field to Logo.dev.

Onboarding personalization

Brand a signup flow from a work email.

API keys

Where secret and publishable keys live and how to use each.

API Reference

Products

Brand API: Company Brand Assets by Domain

What a brand API does

What’s in the response

One request instead of a pipeline

Authentication and plans

Next steps

Get a brand profile

Migrate from Brandfetch

Onboarding personalization

API keys

​What a brand API does

​What’s in the response

​One request instead of a pipeline

​Authentication and plans

​Next steps

Get a brand profile

Migrate from Brandfetch

Onboarding personalization

API keys

What a brand API does

What’s in the response

One request instead of a pipeline

Authentication and plans

Next steps