A change in one environment doesn’t reach another until you it.
API keys
Every API key belongs to one environment, and the key you call Courier with decides where the request lands. Courier has no separate test mode: a Test key is what puts you in the Test environment. The prefix tells you what the key can do:
Create a separate key for each service so you can rotate or revoke one without breaking the others. Use API keys only in server-side code, and use Test keys during development. A browser or mobile app signs in with a JWT that your backend mints, as shows.
Create and rotate keys in .
Production, Test, and custom environments
Every workspace starts with Production and Test. You can create as many custom environments as you need, such as Staging or QA. To create one, open the environment dropdown at the top of the console and select Create new environment. You can rename any environment except Production. Switch environments from the same dropdown. Switching changes only your view, never live notifications.Email in the Test environment
A new workspace’s Test environment comes with a testing email provider already configured, so you can send before connecting anything of your own. That provider only delivers to the address you signed up with. You can develop against real sends with no chance of reaching a customer, which also makes a Test key the right one to hand an . To reach other addresses from Test, connect your own email provider to that environment, such as a sandbox SendGrid key. Integrations are per environment, so this doesn’t change Production.Migrate assets between environments
To copy a template to another environment, open the ellipsis menu on the template in the templates page and choose Migrate assets. Courier copies the template with its dependencies: brands, tags, subscription topics, test events, and event maps. On later migrations, you choose whether to overwrite each copied dependency or keep the one already there. To copy to another workspace, pick it as the destination. Provider integrations stay in their own environment and aren’t copied. Before you send from a migrated template, configure its providers in the destination environment. The destination can use different credentials from the source.Logs and metrics by environment
Logs and metrics belong to the environment of the key that made the send. A Test-key send appears only in the Test environment’s logs, and a Production-key send only in Production’s.FAQ
Should I use separate workspaces or environments for staging?
Should I use separate workspaces or environments for staging?
Environments are the right fit for staging. Create a custom Staging environment in the same workspace. Separate workspaces are for separate billing, not for staging.
Why does a migrated template render but not deliver?
Why does a migrated template render but not deliver?
Provider integrations are per environment and aren’t migrated. Configure the provider in the destination environment so the template has a channel to send through.