Blog
ENGINEERINGCOURIER

How to White Label Email Notifications for Multiple Brands

Riley Napier

December 15, 2020

Brands-Courier-Hero

Table of contents

Whitelabeling your email notifications in Courier

Get started with Brands

Whitelabeling emails is the process of transforming your emails, so that they look like they're coming from another brand. Imagine, for example, that you're an employee management platform that sends engagement surveys, check in-reminders, and other alerts on behalf of your customers. You and your customers will likely want those email notifications to match the employer's brand, not yours.

But, if you've ever had to whitelabel emails before, you know it can be a real headache. At an e-commerce platform where I worked previously, our customer service team would contact our clients one by one to get their logo and other assets and use a custom dashboard to upload each brand into our system. Then, on the engineering side, we'd write custom logic for our templates with conditionals for the different brands, pulling the brand IDs from our CMS. And, in some cases, we'd even write a hardcoded template for a specific brand.

That's precisely why we built Brands at Courier. Brands makes it easy to send whitelabeled notifications that match your customers' brands or, if you have multiple properties, your own sub-brands. As a developer, you can also create, update, and delete Brands programmatically with our Brands API, which saves a ton of time and effort.

In this post, I'll explain how you can create and send whitelabeled email notifications using Courier's Brands feature.

Whitelabeling your email notifications in Courier

Creating multiple brands

You can quickly create new brands through our UI or programmatically with our Brands API. When you create a new Brand, you have the option to configure the brand colors, the header and footer, and any social media links. You can even add custom CSS to the header, footer, and head section to have it fully match your customers' brands or your sub-brands.

Creating a Brand in Courier

Creating custom, reusable code with Snippets

You can extend the Brands you create in Courier with Snippets. Snippets are pieces of code that you can reference in the templates for your notifications. Returning to our earlier example, if you were an employee management platform, you might create a Snippet for each of your customers' brands that includes their mission statement. Now, instead of copy-pasting across each template, you can simply call the Snippet by name.

Create a Snippet for a Brand in Courier

You can also use variables to customize your Snippet. You could, for instance, create a variable for your customers' mission statements. Then, you could reuse one template across all your Brands. When you send your notification, all you would have to do is include the correct Brand ID and supply the right value for the variable in your API call to Courier.

Like everything else about Brands, Snippets can be managed programmatically with our Brands API or customized in the UI.

Sending whitelabeled emails using Brands

Once you've set up your Brands, sending whitelabeled email notifications is super straightforward. You can either choose a specific Brand in the UI or you can set the Brand programmatically by including the Brand ID in your API call to Courier.

Preview your Brand in Courier

Get started with Brands

Ready to get started with Brands? Sign up for free – you can create up to 10 Brands and send up to 10,000 notifications free every month.

If you want to learn more about Brands, check out our livestream where Aydrian, our Staff Developer Advocate, walks you through how to create and send a notification with multiple Brands using the Courier API and Python SDK. You can also find additional code samples on Github – we offer libraries for Python, Ruby, Node, Go, and PHP.

Curious how we built Brands? Stay tuned for a look under the hood!

Similar resources

courier and expo push notifications
GuideEngineering

Expo Push Notifications: The Complete Implementation Guide (SDK 52+)

Expo push notifications are alerts sent from a server to a user's phone, even when the app isn't open. To set them up, install the expo-notifications library, ask the user for permission, and get a unique push token for their device. Your server sends a message to Expo's push service with that token, and Expo delivers it through Apple or Google. Push notifications only work on real phones, not simulators. Local notifications are different — they're scheduled by the app itself for things like reminders. You can also route Expo push through services like Courier to add email, SMS, and Slack fallbacks.

By Kyle Seyler

February 24, 2026

email infrastructure providers
AIGuideEngineering

Best Email API Providers for Developers in 2026: SendGrid vs Postmark vs Mailgun vs SES vs Resend

Your email provider sticks with you longer than most technical decisions. Courier handles notification infrastructure for thousands of teams, so we went deep on the six email providers that show up most: SendGrid, Postmark, Mailgun, Amazon SES, Resend, and SMTP. This guide covers real API primitives, actual code from each provider's docs, Courier integration examples with provider overrides, and an honest read on where each developer experience holds up and where it breaks down. We also asked Claude to review every API and tell us which one it would wire up first. The answer surprised us.

By Kyle Seyler

February 23, 2026

Courier MCP is open source
AIEngineering

The Courier MCP Server Is Open Source. Here's How It Actually Works.

Courier's MCP server is open source at github.com/trycourier/courier-mcp. It connects AI coding tools like Cursor and Claude Code to your Courier account so they can send messages, manage users, and install SDKs without hallucinating API details. This post walks through the actual codebase: how 16 tool classes are registered (and how a config allowlist gates most of them), why we pull installation guides from GitHub at runtime instead of bundling them, how the DocsTools class generates live JWTs alongside setup instructions, and what the SdkContextTools class does in the repo to prevent v7/v8 SDK conflicts (even though it isn't wired into the server yet).

By Mike Miller

February 06, 2026

Multichannel Notifications Platform for SaaS

Products

Platform

Integrations

Customers

Blog

API Status

Subprocessors


© 2026 Courier. All rights reserved.