API Workbench

Run Real API Requests

Tune the payload, press send, and the request executes against an isolated ApexMail sandbox with a real API key — real validation, real queuing, real delivery attempts, and the verbatim response.

How the sandbox works

Requests run against an isolated ApexMail sandbox — the same handlers, queue and worker as production.

Sandbox messages cannot be delivered to real recipients: every recipient must end in @example.com (RFC 2606 reserved).

Responses are the real status codes, latency and JSON bodies — not simulations.

Endpoints

Pick a lane, tune the JSON payload, then send — the request executes against the live sandbox API and the response page shows the real status, latency and body.

Send-lane recipients are limited to the reserved example.com domain; messages really queue, the worker really attempts delivery, and the full lifecycle is visible in the Messages lane.

POST/v1/messagesSandbox

Response Inspector

Press Send — the request executes against the live sandbox and this panel renders the real response on the result page.

Real handlers, real queue
Real idempotency semantics
example.com recipients only
GET/v1/messages?limit=20Sandbox

Delivery stream and lifecycle lookup — the sandbox tenant's own messages, including everything you sent above.

GET/v1/domainsSandbox

Identity posture and DNS verification status for the sandbox tenant's domains.

POST/v1/domainsSandbox

Response Inspector

Provisions a subdomain of example.com in the sandbox and returns the real creation response with DNS records.

Ready to Build?

Go from Playground to Production

Sign up free: 3,000 emails per month plus a one-time 30,000-email launch allowance for your first 30 days. Same API, same reliability, your own API keys.

Start Free Read Documentation
Available SDKs
PythonRubyGoPHPJava