Why do I get 403 unverified_workspace_recipient?

This article explains the 403 Workspace not verified error that new workspaces get when they send to outside addresses, and how to lift the restriction.

Symptoms

POST /v2/emails returns 403 with a body like this:

{
  "code": "unverified_workspace_recipient",
  "error": "Workspace not verified",
  "message": "Unverified workspaces can only send to workspace members' account emails. Blocked recipient: ada@example.com.",
  "blocked_recipients": ["ada@example.com"]
}

You may also see:

• SMTP rejects the recipient with 550 Unverified workspaces can only send to workspace members' account emails.
• Campaigns fail with Unverified workspaces cannot send campaigns.
• The dashboard shows the banner This workspace is not verified. Emails can only be sent to workspace members’ account emails.

Cause

Every new workspace starts unverified, in a sandbox. Until the Emailit team approves the workspace for production access:

• You can send only to the account email addresses of workspace members, meaning the addresses people use to sign in. Pending invitations don’t count.
• If any to, cc or bcc address is outside that list, the whole request is rejected and no credits are charged. The blocked_recipients array lists the addresses that caused it.
• Campaigns can’t be sent at all.

This protects shared sending reputation from abuse by brand-new accounts.

Fix

1. Verify a sending domain. Production access requires at least one verified domain. Add one in Email API›Domains and publish its records. See Add a domain.

2. Open the request form. Select Request production access on the dashboard banner, or go to Workspace›Settings, open Requests and choose Request Workspace Verification. Only workspace admins can submit it.

3. Describe your sending honestly. Choose the email type (Transactional, Marketing or both), your website URL, expected monthly volume and use case, explain how you collect recipients, and confirm the compliance checkboxes. Specific answers get approved faster.

4. Watch the request thread. The request shows Pending Review while the team looks at it. If it changes to Awaiting Your Reply, answer the question in the thread. When it’s Approved, the restriction is lifted right away.

5. Keep testing in the meantime. Send to your own account email, or invite teammates so their addresses become allowed once they accept. See How do I test sending before my workspace is verified?.

Read Production access for the full review process and API errors for other 403 responses.

Still stuck?

If your request has been pending for a while, reply in the request thread, contact support or ask in Discord.