Frequently asked questions

Ask the deployment owner for the public HTTPS origin, SMTP host, port, TLS mode and certificate details. Source defaults are not verified public endpoints. This page performs no real connection tests.

Match the returned TXT name/value with your provider’s format, wait for propagation, and inspect each check. HTTP 200 does not mean all_passed. Do not publish a demo public key or assume an SPF include. Contact support for node deployment issues.

Use an API Key rather than a session token, check that it has not been revoked and the account is usable. The sending domain must be verified and within the key’s scope. Successful key verification does not guarantee quota.

No. 202 means accepted into the queue. sent can mean node acceptance and guarantees neither inbox placement nor reading. Check status and Webhooks. Sending has no idempotency key; blind retries after a timeout can duplicate messages.

SMTP and Email API share account quota; each domain does not get its own allocation. Daily and hourly limits use fixed UTC day/hour windows, not rolling 24 hours. Total, daily and hourly limits all constrain sending. Failed requests are not guaranteed an automatic refund. max_domains remains a hard domain limit.

The current API supports one-time plans. FIFO queues, activation-based validity months and automatic switching are not live. Confirm actual account entitlements before purchasing; this page promises neither queued purchases nor automatic succession.

New-sales targets do not automatically cancel historical monthly/yearly subscriptions or change purchased rights. Renewals, refunds and migration need separate verification; this guide makes no promise about outcomes. Use the existing console ticket system with error code, time and message ID, never a full API Key or Webhook secret.