Skip to main content
You need an enabled Mail connection, a verified sender domain and a Webdock Mail API key. Keep the key in a private server-side environment variable named WEBDOCK_MAIL_API_KEY.
1

Prepare the sender

Follow Mail setup. Replace the example sender below with an address on your verified domain.
2

Use a simulator recipient

The delivered@test.mail.webdock.dev recipient simulates delivery without sending to an external inbox. Simulator results do not prove live provider delivery.
3

Submit once

Use one stable idempotency key for the logical message. Keep the same body and key when retrying that request.

Inspect the result

Save the returned message ID and inspect its state in Console. Reading message details through the API requires full_access; a sending-only key is deliberately narrower.
If the API reports send_outcome_unknown, inspect its existing email_id. Never switch to a new idempotency key to force a resend: the original may already have reached the provider.
An accepted response is not proof of delivery. Use message events and recipient state. Before sending to a real recipient, confirm that your connection’s live dispatcher and event processing are enabled. Continue with Mail API behavior and webhooks.

Existing Auth-host clients

The previous https://auth.webdock.dev/api/mail/v1 base remains an alias. Use the API host for new integrations. Both addresses share keys, quotas and idempotency records; changing host is not a reason to resend an uncertain message with a new key.