Mailivate reviews new sending accounts before campaigns, automations, and transactional API mail can go live. This protects recipients and shared sending reputation.
Transactional API mail (POST /api/email) uses this same approval flow. It also requires a verified transactional domain.
How to request approval
- Open Settings → Request Approval.
- Answer every required question honestly:
- Planned monthly volume
- Whether you are bringing an existing list
- How people opt in
- How you acquire subscribers
- Websites where you collect addresses
- Why you chose Mailivate
- Optional past sending stats
- Submit. Status becomes pending.
- When Mailivate approves the request, you can send campaigns, automations, and transactional email (campaigns still need a plan, business address, and marketing domain).
You cannot submit a second request while one is pending. If you are already approved, the page will tell you.
What reviewers look for
- Permission-based lists (no purchased, rented, or scraped addresses)
- A clear opt-in process
- Realistic volume
- Websites that match the brand you will send as
Incomplete or inconsistent answers delay approval. If you are in a higher-risk industry, say so up front — see the Acceptable Use Policy on mailivate.com.
After you submit
| Status | What it means |
|---|---|
| Pending | Wait for review. You can still verify domains, build lists, and send tests where the UI allows. Transactional API sends stay blocked. |
| Approved | Live campaign, automation, and transactional sends are allowed (other requirements still apply). |
| Rejected | Fix the issues described, then contact support if you need to re-apply. |
If send fails with an “account not approved” error, this is the missing step.
Next: Send your first email.