Include this and it gets solved faster
- The inbox address or phone number involved — never the token.
- What you called and what came back: the endpoint, and the HTTP status and
codefield of the error. - Roughly when it happened, with a timezone.
- For a payment problem, the Solana transaction signature.
Things that are usually not bugs
- The mail never arrived.
- Check the inbox still exists. A free inbox deletes itself 24 hours after
its last activity, and a sender writing to an address that no longer exists
gets a hard rejection.
GET /api/v1/inbox/:addresstells you immediately. - The code arrived but the OTP field is empty.
- The extractor recognises the common formats, not all of them. The full message body is always in the mail itself — parse it yourself and tell us the format so we can add it.
- Sending returns
send_disabled. - The inbox crossed the bounce or spam-complaint threshold and outbound was cut automatically to protect delivery for everyone. Write to us; it is reversible once the cause is understood.
- A custom-domain inbox cannot send.
- By design. Delegated domains receive only — sending stays on
@apumail.com. - Push notifications do not arrive on the phone.
- Check notification permission for the app in the system settings, and that the inbox is registered on that device. Notifications only ever show the sender and subject, never the body.
Documentation
/llms.txt is the quickstart — written to be read by an agent, and short enough to read yourself. /openapi.json is the full API, the MCP descriptor wires it into an MCP client, and the blog has worked examples.
Security
Report vulnerabilities to support@apumail.com before disclosing them publicly. We will confirm receipt and keep you posted on the fix.