Skip to main content
Live email normally comes from a domain you have verified. Many teams only get their domain, or access to its DNS, when they are close to production. Until then you can still see Sendbaze deliver a real email by sending from the shared test address:
It works with a live key and from the Domains page of the dashboard, and the email takes the same path a customer email takes: queued, signed by Amazon SES in Cape Town, delivered, and reported in Logs and by webhooks.

The rules

The shared address is a taste of the product, not a way to send without a domain. Three limits keep it that way: Both errors carry a domainsUrl pointing at the Domains page, where the fix always is: add and verify your own domain, and send from it to anyone.
Test keys (sk_test_) are different: they validate the request and store the message but never deliver, so they are not subject to these rules. Use a test key in CI and the shared address when you want to see an email arrive.

Send one

Put your own sign-in email in to.
Response
A display name before the address is fine; the address itself must be exactly onboarding@sendbaze.com. From the dashboard, open Domains: until one of your domains is verified the page offers Send test email from the shared address to your own inbox and shows how many of the 100 are left.

When it is refused

Response (403)

Move to production

1

Add and verify your domain

Follow Add and verify a domain. Most domains verify within half an hour of publishing the records.
2

Change from

Send from an address on your domain, for example orders@yourshop.co.za. From that moment the recipient rules and the lifetime total no longer apply.
3

Pick a plan for your volume

The Free plan includes 3,000 emails a month with a daily cap of 150. Compare plans when you send more.
Do not use made-up addresses on example.com or similar for testing. They bounce, and hard bounces are added to the suppression list and count against your reputation. Use your own address, or the simulator addresses.