weneed.email

weneed.email sends transactional email for your application: sign-in links, one-time codes, receipts, notifications. You connect over an HTTP API or SMTP. Both lead to the same queue, the same message history and the same rules.

How a message travels

1. Your application submits a message with a credential for one project.
2. weneed.email checks the sender, your permissions and your remaining allowance.
3. The message is stored durably. Only then do you get 202 (API) or 250 (SMTP).
4. A worker delivers it directly to the recipient’s mail server and records the result.
5. If the recipient’s server reports a failure later, it is linked back to your message. A permanent failure suppresses that address, so you don’t keep sending to it.

A 202 or 250 means stored and queued, not delivered. Delivery is a separate, later fact in the message history.

Before your first message

• Connect your domain and publish the DNS records.
• Understand why a verified domain doesn’t let you send yet.
• Pick a path: first send via API or via SMTP.