Support

How to get help with send.dev

Before you write in

Most questions are answered on one of these pages:

• Quick start, for the first send end to end.
• Domains, for DNS records that will not verify.
• Errors, for what each error code means and whether to retry.
• Rate limits, for 429 responses, the probation caps on new accounts, and the per-domain daily ladder.
• Get an email, for what each delivery status means.

Contact

Email help@do.dev. Replies come from a person, normally within one business day; account pauses are handled faster.

Include what you can of the following. It usually saves a round trip:

1. The email address on your send.dev account.
2. What you were trying to do and what happened instead.
3. The exact error response, including error.code.
4. Relevant ids: the msg_ id of an email, the domain id, or the template id.
5. The approximate time (with timezone) of the request.
6. A sanitized copy of the request, with the API key removed.

Paused accounts and held domains

If your account shows sending_paused, reply to the notification email you received or write to help@do.dev with what changed in your sending so we can look at the bounce and complaint data together. New accounts are paused automatically on early bounces or complaints; see Rate limits.

Domains are approved automatically on verification. In the rare case a domain tripped an abuse check and shows pending_approval after verifying, you will receive an email when it is decided; there is no need to write in unless it has been more than a business day.

Volume increases

Need more than the per-domain daily ladder allows for a launch? Write ahead of time with the domain, the date, and the expected daily volume and list source.

Security issues

Report vulnerabilities to help@do.dev with reproduction steps. Please give us a reasonable window to fix the issue before disclosing it publicly.