InboxFlick / docs

Resources

About & usage policy

InboxFlick’s free API exposes its own temporary receiving service. It does not proxy Mail.tm.

What is free

Creating, selecting, extending and deleting temporary inboxes; listing, reading and deleting messages; domain discovery; and live receive notifications. No account, subscription or API key is required. Fair-use limits apply equally to scripts and website clients. This is the InboxFlick API, with its own paths, cookie authentication and response envelope. It is not a drop-in replacement for Mail.tm accounts or bearer tokens.

Acceptable use

Use the API for authorized development tests and short-lived tasks. Commercial application integration is allowed within the same free limits. Do not use it for spam, fraud, harassment, unauthorized account creation, evading platform restrictions, or collecting other people’s mail. Do not bypass quotas through IP rotation, resell shared access as guaranteed capacity, or present this shared service as an SLA-backed private deployment. We may limit abusive traffic. Follow the main InboxFlick terms and privacy notice.

Privacy and retention

Inboxes start at 10 minutes and can be extended before expiry up to 60 minutes from creation. Expiry or manual destruction revokes access and starts cleanup. No permanent storage, recovery or guaranteed third-party delivery is offered. Avoid banking, medical, work, or other important accounts. Only a hash of the possession credential is stored server-side. Keep your local cookies private. The API does not support SMS, outbound mail, forwarding or permanent accounts in this free flow.

Availability and support

This is a free shared service with no SLA. Limits, domains and availability may change. Check error.code, respect retry guidance and use a permanent address where continuity matters. For support, use the contact address on the InboxFlick website and include only the request_id, time and non-sensitive reproduction steps. Never share session cookies or private message bodies.

Search documentation

Temp Mail APIFree temporary email API for development and short-lived workflows. Create private inboxes, receive messages, and clean up with a cookie-aware client.AuthenticationNo account, password, or API key. Keep a private cookie jar for each independent client.Error handlingUse the HTTP status and stable error.code. Responses contain a request_id for support.DomainsDiscover the receiving domains configured for free temporary inboxes.MailboxesCreate and manage a short-lived inbox using its private possession cookies.MessagesList, read, and delete messages inside the selected inbox. IDs never grant access by themselves.Real-time eventsReceive message.received notifications through an authenticated server-sent event stream.IntegrationsKeep cookies between requests. Run one isolated session per independent test workflow.About & usage policyInboxFlick’s free API exposes its own temporary receiving service. It does not proxy Mail.tm.