Test in a sandbox

Before you start

An owner or administrator creates sandboxes from the live company’s settings. A sandbox has its own data and API keys. Emails are kept in its inbox; confirmed test addresses are the explicit exception for testing real delivery.

Create and open a sandbox

1. Open Settings › Sandboxes in your live workspace.
2. Create a sandbox, give it a recognizable name and choose who can access it.
3. Choose whether to copy from your live company, then confirm creation.
4. Open the sandbox. Check the sandbox indicator before changing settings or running a test.

Check your test emails

Send a campaign, run a flow or send a transactional email inside the sandbox. Open the sandbox inbox while that sandbox is selected and inspect the message. This confirms what Azimea generated; it does not measure placement in a real recipient’s inbox.

To test delivery to an address you control, return to the live company’s sandbox settings, open Test addresses for that sandbox and add the address. Complete the confirmation sent to it before using it for a delivery test.

Test an integration

Create an API key while inside the sandbox. It starts with azm_test_. Use that key in your integration and keep it separate from live credentials. Delivery webhooks can still call your configured receiver: use a test receiver if it would otherwise change production data.

See API authentication and sandbox webhooks.

If a test does not appear

Check	Next step
Are you in the right workspace?	Select the sandbox used by the campaign, flow or API key, then reopen its inbox.
Was the email suppressed?	Read the reason in sending restrictions.
Are you checking a real mailbox?	Confirm that address under the sandbox’s test addresses, or inspect the internal inbox instead.

Move to live

Return to your live workspace and check its domain, consent settings and sender before publishing. Use a live API key only when you intend to send real messages. Sandbox API keys continue to operate on sandbox data.