Skip to content
Docs

FAQ

How do I test sending before my workspace is verified?

Unverified workspaces can send to their members' account emails. Use that to test the API, SMTP, templates and campaigns while production access is reviewed.

Updated Oct 1, 2026

You can build and test your whole integration before Emailit approves your workspace. This article explains what an unverified workspace can send and how to test each sending method.

Symptoms

  • Your workspace shows the banner This workspace is not verified. Emails can only be sent to workspace members’ account emails.
  • Test emails to colleagues or test inboxes fail with 403 unverified_workspace_recipient.
  • You want to finish your integration while your production access request is reviewed.

Cause

New workspaces start in a sandbox. Until production access is approved:

  • You can send to the account email addresses of workspace members, the addresses people sign in with. Members who haven’t accepted their invitation yet don’t count.
  • Addresses must match exactly. A plus-addressed variant such as ada+test@acme.com isn’t on the list.
  • Campaigns can’t be sent to audiences, but campaign test sends to members work.
  • Everything else works normally: domains, API keys, templates, webhooks and logs. Test emails use credits like any other email.

Fix

  1. Verify a sending domain. You need one to send at all. See Add a domain.

  2. Send yourself a test from the dashboard. In Email APIEmails, select Compose, choose your domain and send to your own account email. Compose is limited to 3 emails a minute and 10 an hour per workspace.

  3. Test the API or SMTP against your own address. Create a key in Email APIAPI Keys and follow the API quickstart or the SMTP quickstart. Use your account email as to.

  4. Add teammates as recipients. Invite colleagues in WorkspaceSettings under Members. Once they accept, their account emails become valid test recipients. See Invitations.

  5. Test campaigns with test sends. In the campaign editor’s preview step, send a test to up to 5 member addresses. See Test and schedule.

  6. Test webhooks without sending. On a webhook’s page, use Send test to post a sample event of any type to your endpoint.

  7. Request production access. When you’re ready to send to real recipients, submit Request Workspace Verification under Requests in WorkspaceSettings. See Production access.

Inbox-placement testers and seed lists use addresses outside your workspace, so they only work after approval. For the error response, see Why do I get 403 unverified_workspace_recipient?.

Still stuck?

Contact support or ask in Discord if a test to a member address is still blocked.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.