Hostinger Mail

Return the full OpenAPI 3 document for the Hostinger Email API (mailboxes, folders, messages, send, webhooks). Use when you need the complete schema; otherwise prefer email_list_operations + email_describe_operation.

Delete via the Hostinger Email API (destructive, irreversible). Use for DELETE calls: delete a message, delete a webhook, etc. Bearer auth is forwarded automatically — never include tokens in arguments. Returns {status, headers, body}.

Read from the Hostinger Email API (safe, read-only). Use for GET/HEAD calls: list messages, fetch a message body, list folders, read webhooks, GET /api/v1/me, etc. Need a mailboxResourceId? Call GET /api/v1/me first — response data.mailboxes[] contains all mailboxes for the order. Bearer auth is forwarded automatically — never include tokens in arguments. Returns {status, headers, body}.

Create or modify via the Hostinger Email API. Use for POST/PUT/PATCH calls: send email, move/flag messages, create or regenerate webhooks, etc. This tool never issues DELETE requests, but some actions such as sending email or regenerating webhook secrets can be irreversible. Need a mailboxResourceId? Call GET /api/v1/me (via email_call_api_read) first. Bearer auth is forwarded automatically — never include tokens in arguments. Returns {status, headers, body}.

Return the OpenAPI operation object (parameters, request body schema, responses) for one Hostinger Email endpoint identified by method+path. Use before calling email_call_api_read/write/delete so you know exactly what arguments are required.

List available Hostinger Email API operations (method, path, summary, tags). Use this first to discover endpoints for reading mailboxes/folders/messages, searching emails, sending, or managing webhooks. Filter by tag like 'Messages', 'Mailboxes', 'Folders', 'Webhooks', 'Send'.