Send from your own domain

Set the address your email comes from, then override it for one template or one send.

What you will build

Set the integration default once. Reach for the other two only when a template or a single message needs a different sender.

Prerequisites

A domain you control, with access to its DNS records

Set the sender

Verify the domain at your provider

Courier does not verify domains. Your email provider does, and it enforces the result when the message goes out.Add the DKIM and SPF records your provider asks for, then wait for it to mark the domain verified. SendGrid’s Sender Authentication and Amazon SES verified identities are the two most common.An unverified domain fails at the provider, not in Courier. The message lands in as undeliverable with the provider’s error attached.

Set the From Address on the integration

Open your provider in and set From Address to an address on the verified domain. Every email through that provider uses it unless something below overrides it.Some providers also have a From Name field. Where there is none, put the display name in the address itself.

Acme Support <support@acme-corp.com>

Override it for one template

Open the template’s email channel and fill From in the subject bar. It takes the same Name <email> form, and it accepts , so one template can send as a different address per message. Reply-To, CC, and BCC sit beside it. covers all four.

Override it for one send

A request carries message.channels.email.override.from, which replaces the sender for that message alone, whichever email provider ends up sending it.

const { requestId } = await courier.send.message({
  message: {
    to: {
      user_id: "user_123",
    },
    template: "nt_01kx4h2jdafq8bk9aftxak4b40",
    channels: {
      email: {
        override: {
          from: "Acme Support <support@acme-corp.com>",
        },
      },
    },
  },
});

response = client.send.message(
    message={
        "to": {
            "user_id": "user_123",
        },
        "template": "nt_01kx4h2jdafq8bk9aftxak4b40",
        "channels": {
            "email": {
                "override": {
                    "from": "Acme Support <support@acme-corp.com>",
                },
            },
        },
    },
)

curl -X POST https://api.courier.com/send \
  -H "Authorization: Bearer $COURIER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": {
      "to": {
        "user_id": "user_123"
      },
      "template": "nt_01kx4h2jdafq8bk9aftxak4b40",
      "channels": {
        "email": {
          "override": {
            "from": "Acme Support <support@acme-corp.com>"
          }
        }
      }
    }
  }'

response = courier.send_.message(
  message: {
    to: {
      user_id: "user_123"
    },
    template: "nt_01kx4h2jdafq8bk9aftxak4b40",
    channels: {
      email: {
        override: {
          from: "Acme Support <support@acme-corp.com>"
        }
      }
    }
  }
)

response, err := client.Send.Message(context.TODO(), courier.SendMessageParams{
	Message: courier.SendMessageParamsMessage{
		To: courier.SendMessageParamsMessageToUnion{
			OfUserRecipient: &shared.UserRecipientParam{
				UserID: courier.String("user_123"),
			},
		},
		Template: courier.String("nt_01kx4h2jdafq8bk9aftxak4b40"),
		Channels: shared.MessageChannelsParam{
			"email": shared.ChannelParam{
				Override: map[string]any{
					"from": "Acme Support <support@acme-corp.com>",
				},
			},
		},
	},
})

SendMessageParams params = SendMessageParams.builder()
    .message(SendMessageParams.Message.builder()
        .to(UserRecipient.builder().userId("user_123").build())
        .template("nt_01kx4h2jdafq8bk9aftxak4b40")
        .channels(MessageChannels.builder()
            .putAdditionalProperty("email", JsonValue.from(
                java.util.Map.of("override", java.util.Map.of(
                    "from", "Acme Support <support@acme-corp.com>"))))
            .build())
        .build())
    .build();
SendMessageResponse response = client.send().message(params);

$response = $client->send->message(
  message: [
    'to' => [
      'user_id' => 'user_123',
    ],
    'template' => 'nt_01kx4h2jdafq8bk9aftxak4b40',
    'channels' => [
      'email' => [
        'override' => [
          'from' => 'Acme Support <support@acme-corp.com>',
        ],
      ],
    ],
  ],
);

SendMessageParams parameters = new()
{
    Message = new()
    {
        To = new UserRecipient { UserID = "user_123" },
        Template = "nt_01kx4h2jdafq8bk9aftxak4b40",
        Channels = new Dictionary<string, Channel>
        {
            {
                "email",
                new Channel
                {
                    Override = new Dictionary<string, JsonElement>()
                    {
                        { "from", JsonSerializer.SerializeToElement("Acme Support <support@acme-corp.com>") },
                    },
                }
            },
        },
    },
};

var response = await client.Send.Message(parameters);

courier send message \
  --api-key "$COURIER_API_KEY" \
  --message.to '{"user_id": "user_123"}' \
  --message.template nt_01kx4h2jdafq8bk9aftxak4b40 \
  --message.channels '{"email": {"override": {"from": "Acme Support <support@acme-corp.com>"}}}'

With Courier MCP, send my nt_01kx4h2jdafq8bk9aftxak4b40 template to user_123 from Acme Support <support@acme-corp.com>.

How the levels resolve

Every email provider resolves the sender the same way, taking the first one set:

Order	Where it comes from	Scope
1	`message.channels.email.override.from`	One message
2	The template’s email From field	Every send of that template
3	From Address on the provider integration	Every email through that provider

Nothing set at any level is a send-time error, not a silent fallback to a Courier address. A few providers also accept a sender inside a provider override, such as message.providers.postmark.override.config.fromAddress. That form is provider-specific, and where it sits in the order above varies by provider, so check the provider’s page before relying on it.

Verify

Send a test, open the message in , and read the Raw tab. It shows the request Courier made to the provider, which is the only place the final sender appears. Courier applies overrides after rendering, so the Rendered tab shows the pre-override value.

FAQ

Why is my template's From field ignored on Gmail?

Gmail sends as the authorized inbox, so the From address is always the connected Google account. A template From field has no effect there. Set the display name with the integration’s From Name, and change the address by authorizing a different inbox.

My provider has no From Name field. How do I set a display name?

Put it in the address: Acme Support <support@acme-corp.com>. Most email providers have no separate name field, so this form is how you set a display name.

Can a brand control the sender?

carry visual styling only, with no sender field of any kind. The sending address is provider and template configuration.

Is a branded tracking domain the same thing?

Link and open tracking uses a separate CNAME to Courier’s tracking infrastructure, set up independently of your sending domain. See .

Get started

Send your first message

Build a notification

Send to many people

Send when something happens

Let users choose

Go live

Move to Courier

Send from your own domain

What you will build

Prerequisites

Set the sender

Override it for one template

Override it for one send

How the levels resolve

Verify

FAQ

​What you will build

​Prerequisites

​Set the sender

​Override it for one template

​Override it for one send

​How the levels resolve

​Verify

​FAQ

What you will build

Prerequisites

Set the sender

Override it for one template

Override it for one send

How the levels resolve

Verify

FAQ