Send your first email
Set up a sender domain and address, then send and verify your first test email.
Send your first test email with the Email product: prepare an API Key and sender identity, submit a single-send request, then look up the final result by Message ID. This flow uses a Bearer API Key. The browser testing dialog does not need an API Secret. A test request submits real email.
Acceptance is not delivery
code=000000 means the platform accepted the request. Check send records for the outcome. “Delivered” means the receiving server accepted the message, not guaranteed inbox placement or reading.Before you begin
- The Email product is enabled for your account, and you have an active API Key from Console > Developers.
- Your outbound IP satisfies the API Key allowlist.
- You control a sending domain and have completed domain verification and sender-address setup in the email console.
- You have an authorized test recipient. Do not put an API Key, API Secret, or real recipient data in public docs, screenshots, or logs.
Send your first email
Check the sender identity
Confirm that the sending domain and sender address are ready. If needed, use the sending-domain guide to add the domain, publish the DNS records shown in the console, and complete any required review.Choose how to send
Open API Reference · Send one email and select interactive testing with a Bearer API Key. You can also call the same endpoint from a controlled server. Interactive testing supports Bearer API Key for single and batch sending.Fill in the test request
Set a uniqueX-Idempotency-Key and enter an authorized sender, test recipient, subject, and body. Replace the example addresses below with your own test addresses.Check acceptance and delivery
Confirm HTTP 202 withcode=000000. Save data.messageId and the X-Request-Id response header, then look up the complete Message ID in send records.Example request body:
{
"from": {"email": "notify@example.com"},
"to": [{"email": "recipient@example.net"}],
"subject": "First test email",
"text": "This is a test message.",
"messageType": "TRANSACTIONAL"
}For a direct server-side call, obtain the HTTPS API host from the platform and send JSON to POST /innomail/v2/messages/send with Authorization: Bearer <API_KEY>, Content-Type: application/json; charset=utf-8, and X-Idempotency-Key. The example addresses are placeholders, not platform sandbox addresses or guaranteed-delivery recipients.
Troubleshooting
| Symptom | Check first |
|---|---|
| 401 or 403 | API Key status, Bearer value, and outbound IP allowlist. |
| 400 | Sender, recipient, subject, body, and idempotency key. |
| 202 but no email | Search send records by Message ID; check sender authorization, suppression, channel failures, and recipient policy. |
| Timeout or 5xx | Reconcile the original task. Keep its body and idempotency key when retrying. |
Next steps
Last updated on