Skip to main content
A list full of gray placeholder avatars reads as unfinished. The same list with every company’s real logo reads as authoritative, and it’s the difference between a text database and a product people trust. Whether the records are CRM accounts or job listings, the pattern is the same two tiers: the Logo API covers every list view with a plain <img> tag, and the Brand API fills detail views with colors, descriptions, and company data. GBM serves over 2.5 million logos a day this way, so investors see a brand instead of a ticker. For customer and partner logos on a marketing page, see Logo walls.

Company directory

CRMs and B2B directories are easier to scan when every account shows the company’s real logo instead of a generic placeholder. For a list of accounts, an <img> pointed at the Logo API is enough, no fetch, no loading state.

Want logo-branded account lists in your app? This prompt gives your AI coding tool everything it needs to build it in your framework.

Open in Cursor

Company detail view

When someone opens a record, the list’s logo is no longer enough, and the Brand API fills in the rest of the page from the same domain: the description, the industry, the company’s size, founding year, and headquarters, and an accent color that gives each record its own look. The request needs your API key, so it runs on the server, and the result can be cached for up to 30 days, which means each company costs one call however many people open it.

Want a company detail view filled from the Brand API? This prompt gives your AI coding tool everything it needs to build it in your framework.

Open in Cursor

CRM contacts

A contact’s work email already says which company they belong to, so a CRM can show the company’s logo next to every person without anyone filling in an account field. Take the domain after the @, skip personal mailbox providers, and pass the domain to the Logo API. When the account also has a cached Brand API record from the detail view, its industry, size, and location make useful tags at no extra cost.

Want company logos on CRM contacts in your app? This prompt gives your AI coding tool everything it needs to build it in your framework.

Open in Cursor

Card grid with hover lift

On grid-based boards, wrap the same data in a card and add a subtle lift on hover so the grid feels responsive to the cursor.

Want an animated job card grid in your app? This prompt gives your AI coding tool everything it needs to build it in your framework.

Open in Cursor

Customer logo walls

Customer and partner logos on a marketing page work differently from logos on records, since a wall of wordmarks needs sizing that balances different shapes and logos that switch versions in dark mode, so they have a page of their own with four examples.

Logo walls and customer logos

A customer logo grid, a scrolling carousel, an animated logo wall, and an inline logo swap, each with code and a prompt.

Implementation

1

Key every record by domain

The domain is the identifier that makes everything else work. If your data only has company names, match them to domains first with the Brand Search API.
2

Lists: Logo API

For rows, cards, and avatars, point an <img> at the CDN, no fetch, no loading state, and fallback/lettermark guarantees a clean monogram for brands not yet in the dataset.
3

Detail views: Brand API

When a user opens a record, fetch the full brand server-side for the description, accent color, and company data, and cache it by domain so repeat visits are free.

Pricing

List views cost nothing, the Logo API is free with a client ID. Detail views cost one Brand API brand fetch per company, and domain-level caching means each company is fetched once, not once per viewer. See plans for quotas.

Going further

Logo API parameters

Sizing, type, theme, and fallback options for every logo.

Brand API reference

The full record: logos, colors, images, and company data for detail views.

Get started

Create a free account and start building.