Check recipient deliverability
Advisory RCPT-time pre-flight check. By default it is the inbound MTA's question: does the recipient exist here, and do its blocklists and routing rules accept this sender? With submission=true it is the submission MTA's question instead: may the authenticated sender (from, judged as /deliver/outbound judges X-Envelope-From for the same caller) submit to this recipient under its OWN rules, the identity's and credential's recipient allowlists, its outbound address lists, and its account's verified-recipients rule? That mode answers nothing about the recipient's existence: an outside recipient is accepted when the sender's rules allow it, and /deliver/outbound at DATA stays the authority for everything else. Its verdict depends on from, so an MTA must never cache it under the recipient alone.
bearerAuthAuthorizationBearer <token>Two credential kinds share this scheme; GET /api/v1/auth/whoami answers which one you hold and what it reaches.
oek_… API key (minted by POST /api/v1/api-keys; shown once at mint). role: account reaches the full account surface: the directory (domains, routes, patterns, api-keys, accounts, address lists) plus every mailbox the account owns. role: system additionally reaches the operator surface, which is documented separately.
oemp_… mailbox app password (minted by POST /api/v1/identities/{identityId}/credentials). Reaches ONE mailbox: its messages, labels, threads, search, sync, send, filters and PIM collections. Directory routes refuse it with 403 insufficient_scope.
Refusal vocabulary: a missing, malformed, expired, or revoked credential answers 401 unauthorized with a WWW-Authenticate: Bearer challenge; a VALID credential outside its scope answers 403 (insufficient_scope for an app password on a directory route, system_credentials_required where only the operator may call). The public routes (health, branding, token-in-path capabilities) declare security: [].
to*stringRecipient email address being checked
1 <= lengthfrom?|Sender email address (MAIL FROM). With submission=true it names the sender whose rules are judged; absent or empty (the null return path), nothing is judged and the recipient is accepted.
ip?|Connecting client IP address
ptr?|Connecting client reverse DNS PTR hostname
helo?|Connecting client HELO/EHLO identity
submission?stringtrue: judge the SENDER's rules for an authenticated submission instead of the recipient's inbound acceptance (default false). Accepted from system and account keys; a sender the caller may not send as, or one that is held, frozen or gone, is accepted here and refused by /deliver/outbound at DATA, which answers it for the whole message.
"true""false"Recipient is accepted: deliverable here (default), or permitted by the sender's own rules (submission=true)
application/json- response
accepted*trueTrue if recipient address is accepted for delivery
truecurl -X GET 'https://api.open.email/api/v1/deliver/check?to=string'{
"accepted": true
}List delivery statuses for a thread or a set of… GET
Batch delivery status, so a thread or a page of the Sent folder costs one request rather than one per message. Exactly one of `threadId` or `messageIds` is…
Submit outbound email message POST
Submits a raw MIME message for outbound relay, local delivery, forwarding, or webhook execution with per-recipient fan-out. Who calls it: the platform's SMTP…