# Prefilling signup from a work email

> Look up the domain of a new user's work email to show their company's logo and colours on the first screen. Which APIs accept an email, and what each costs.

When someone signs up with a work email, the part after the @ is usually their company's domain. A lookup on that domain gives you the company's name, logo and colours, so the first screen can say "Welcome, Acme" with Acme's logo, and a workspace can start in Acme's colours.

## Which APIs fit?

| API | Accepts | Returns | Cost of one lookup |
| --- | --- | --- | --- |
| [Brandfetch](https://brandapis.com/directory/brandfetch) Brand API | An email address, URL or domain | Logos, colours, font names, images, company details | One brand fetch; $0.10 over the plan |
| [Context.dev](https://brandapis.com/directory/context-dev) Brand | A work email, URL or domain | Logos, colours, description, images | 10 credits; not charged if nothing is found |
| [Logo.dev](https://brandapis.com/directory/logo-dev) Brand API | A domain | Name, logos, colours, social links | 5 credits ($0.05) |
| [LogoKit](https://brandapis.com/directory/logokit) Brand API | A domain | Name, logo, colours, company facts | One of the plan's daily Brand Data requests |

Brandfetch and Context.dev take the email itself, so you don't have to cut out the domain.

## What can go wrong?

- **Personal addresses.** A gmail.com or outlook.com address tells you nothing about the company. Skip the lookup for common email providers and ask instead.
- **Sub-brands.** Brandfetch resolves an address to its registrable domain, so `jo@shop.acme.com` returns Acme. A sub-brand that shares its parent's domain gets the parent's brand.
- **Wrong or old data.** Let the user confirm or change what you found. Each provider takes corrections: Brandfetch at brandfetch.com/update, Logo.dev at logo.dev/update, Context.dev at context.dev/update.

## What should you store?

Store what you show, so the next visit doesn't repeat the lookup. Logo.dev lets you keep what its API returns on any plan. Brandfetch lets you cache Brand API data for 30 days, then refresh or delete it. Logo.dev advises storing a brand by its ID rather than its domain, because the ID stays the same when a company changes domain.

## What comes next?

A logo and colours are enough for a welcome screen. If your product then makes work in that company's brand, see [customer brands in an AI product](https://brandapis.com/guides/customer-brands-in-an-ai-product).

---

Source: https://brandapis.com/guides/prefill-signup-from-email
Last updated: 2026-11-10
Published by The Brand API Register. The Brand API Register is run by Rainbrand, which makes one of the APIs listed. Its entry follows the same rules as the others.