Send application email from a verified business domain, with scoped API keys, idempotent requests and delivery events.
Send receipts, account updates and application notifications through POST /v1/emails. Use an active mailbox on a verified domain as the sender. Keep API keys on your server and scope each key to the access your application needs.
Supply an Idempotency-Key with each send request. Reuse that key only when retrying the exact same payload. Scheduling and attachment references let your application prepare a message before it is submitted.
Read message state and events or receive signed webhooks. Verify webhook signatures, check timestamps and deduplicate event IDs. A submitted message has been accepted by the sending mail server; that state does not promise remote acceptance or inbox placement.
Email API access requires platform and organization enablement. Plan allowances, operational limits, sender verification and suppression checks apply. Review the current available capacity before planning volume. RelyPost is designed for transactional messages; it does not provide a newsletter campaign editor.
Yes. Both products can belong to the same organization. They have independent plans and usage. API sending must also be enabled for the service and your organization.
No. Request acceptance, mail-server submission, remote-server acceptance and inbox placement are different outcomes. Inspect the returned state and subsequent delivery events before deciding whether another send is appropriate.
Store the key in your server environment or secret manager. Never embed it in a browser, mobile app bundle or public repository. Revoke a key when it is no longer needed.
Start with your domain. Build a workspace around your team.