Direct POST endpoint for HTML and frontend-hosted forms
Submit straight from static sites, JAMstack apps, or browser forms without building a custom mail backend first.
Deploy contact forms without running mail servers
POST form submissions to MailSlurp and route messages to inboxes or aliases with anti-spam controls and file handling.
Trusted by top companies worldwide
Form delivery
MailSlurp features for form-to-email delivery
Post form submissions straight to MailSlurp, choose how they route, and keep spam and file handling inside the same endpoint.
Explore
File uploads and structured field capture
Send attachments, submitter metadata, and normal form fields in the same request so downstream handlers receive the full submission.
_toAlias and metadata-based routing controls
Route forms to alias IDs or destination inboxes with subject, redirect, and response parameters kept in the submission payload.
Honeypot spam checks and safe public-address handling
Use `_spamCheck` and alias-based destinations so public forms resist bots without exposing real mailbox addresses in client code.
Direct POST endpoint for HTML and frontend-hosted forms
Submit straight from static sites, JAMstack apps, or browser forms without building a custom mail backend first.
File uploads and structured field capture
Send attachments, submitter metadata, and normal form fields in the same request so downstream handlers receive the full submission.
_toAlias and metadata-based routing controls
Route forms to alias IDs or destination inboxes with subject, redirect, and response parameters kept in the submission payload.
Developer integration
Push inbound events into queues, CRMs, and internal systems
Use SDKs and webhook handlers to transform inbound messages into structured downstream work without mailbox sprawl.
- Webhook-first ingestion patterns
- Schema-friendly parsing and extraction
- One integration approach across routing and OCR workflows
Next step
Start with signup or docs
Use the free account to validate the workflow in your own stack, then move into implementation details in the docs.