Troubleshooting
Common useSend errors on the EverJust self-hosted deployment and how to fix them fast.
Common failures when integrating against https://mail.everjust.app/api/v1, with actionable fixes. Most send-time errors trace back to one of two things: useSend's own domain-verification state, or the fact that SES is still in the sandbox.
This is one AWS deployment sending via Amazon SES. Rate limiting is disabled on self-hosted useSend, so a 429 here almost always means you are pointing at the wrong host. See the last item below.
Error envelope
Every API error uses the same shape, so you can match on error.code:
{ "error": { "code": "BAD_REQUEST", "message": "Domain: send.everjust.app is not verified" } }| Code | HTTP | Meaning |
|---|---|---|
BAD_REQUEST | 400 | Malformed body, or domain not verified in useSend |
UNAUTHORIZED | 401 | Missing or invalid Bearer key |
FORBIDDEN | 403 | Key valid but not permitted for this resource |
NOT_FOUND | 404 | No such email, domain, contact, etc. |
NOT_UNIQUE | 409 | Duplicate (e.g. domain already exists) |
RATE_LIMITED | 429 | Not possible on self-hosted — wrong host |
INTERNAL_SERVER_ERROR | 500 | Server-side failure |
Common issues
Still stuck
Sending email
Payload fields, batch, scheduling, and status codes.
Domains
Add and verify sending domains, read DNS records.
Webhooks
Delivery events and signature verification.
If a problem persists after these steps, check the deployment (Terraform infra + MCP server + these docs) at github.com/EVERJUST-DEV/usesend-email.