Skip to main content
1

Get your API key

Copy your Test key from .
2

Send the message

Replace YOUR_COURIER_API_KEY with your key and you@example.com with your own address.
In Test, email only delivers to the address you signed up with.
The meta element’s title becomes the email subject. The <h1> is the heading inside the message, so the two are set separately.See for all the elements you can send.The response returns a requestId:
3

Check the logs

Open to see the delivery timeline.Logs are per , so a missing message usually means a key from the other one.

FAQ

Not to email yourself. Every Test environment ships with the Courier Test Email Provider, which delivers to your signup address only.Any other recipient, or any other channel, needs a provider of your own. connects one and verifies a sending domain.
A holds a notification’s content and behavior in Courier, not in your code. You design it once, then send it by ID and pass only the data.This first send uses inline content so it needs nothing but a key. Most production sends reference a Template, so wording and design change without a deploy.
Test and Production are isolated, with separate keys, Templates, integrations, and logs. Build against Test, then when you go live. Test sends are billable.