What the MailGX API does
The MailGX disposable email API exposes REST endpoints for mailbox lifecycle management and message retrieval. Create an address, trigger your application's email flow, fetch the message body, assert content, and delete the inbox.
No SMTP credentials, no mail server maintenance — just HTTPS calls from your tests or backend services.
Common API use cases
Teams integrate MailGX across the software delivery lifecycle.
- End-to-end signup tests in GitHub Actions or GitLab CI
- Staging verification of password reset and MFA emails
- Load testing transactional email throughput
- Design QA for HTML template rendering
- Demo environments with programmatic inbox creation
Plans and rate limits
Free and premium MailGX accounts include daily API quotas scaled to plan level — from hobby testing to production QA volumes. API keys are managed in the user dashboard alongside usage counters.
See the official API documentation for endpoint schemas, authentication headers, and example curl commands.
Getting started
Create a MailGX account, generate an API key, and read the docs at API documentation. Start with a manual curl request, then wrap calls in your test framework of choice.
Frequently asked questions
Where is the API documentation?
Full endpoint reference lives at API documentation with request and response examples.
Do I need premium for API access?
API access is available on paid plans with daily limits based on tier. Check current plan details on the pricing page.
Can I create multiple inboxes in parallel?
Yes — subject to your plan's rate limits. Parallel inboxes are ideal for concurrent CI jobs.