Send raw MIME email
Send a pre-formatted RFC 2822 MIME message. Use this for advanced use cases or when migrating from systems that generate raw email content.
Important: The rawMessage field must be base64-encoded. Your raw MIME
message (with headers like From, To, Subject, Content-Type, followed by a
blank line and the body) must be encoded to base64 before sending.
Documentation Index
Fetch the complete documentation index at: https://arkhq.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Use your API key from arkhq.io/org/credentials
Authorization: Bearer YOUR_API_KEY
Body
Sender email address. Must be from a verified domain.
Supported formats:
- Email only:
hello@yourdomain.com - With display name:
Acme <hello@yourdomain.com> - With quoted name:
"Acme Support" <support@yourdomain.com>
The domain portion must match a verified sending domain in your account.
1"Acme <hello@acme.com>"
Recipient email addresses
1["user@example.com"]
Base64-encoded RFC 2822 MIME message.
You must base64-encode your raw email before sending. The raw email should include headers (From, To, Subject, Content-Type, etc.) followed by a blank line and the message body.
1The tenant ID to send this email from. Determines which tenant's configuration (domains, webhooks, tracking) is used.
- If your API key is scoped to a specific tenant, this must match that tenant or be omitted.
- If your API key is org-level, specify the tenant to send from.
- If omitted, the organization's default tenant is used.
"cm6abc123def456"
Whether this is a bounce message (accepts null)
