Email Capture

Every endpoint that belongs to an account has an email address next to its HTTP URL. Mail sent to it lands in the same request list as your webhooks, so a signup flow that sends a webhook and a confirmation email can be checked in one place.

The address

The address is the endpoint's slug at mailhooks.cc:

[email protected]

Copy it from the endpoint bar above the request list, or from Settings, under Receiving.

Add a tag after a plus sign to tell test runs or flows apart. Tagged mail lands on the same endpoint, and the tag is shown on the email in the list and in the detail view:

[email protected]
[email protected]

The slug is not case sensitive. The tag is kept exactly as the sender wrote it.

Which endpoints receive email

Endpoints on an account do, on every plan, including endpoints shared with a team. Endpoints created without an account (guest endpoints on the landing page) receive HTTP requests only, because anyone who knows a guest slug can read what it captured. Mail to a guest endpoint is refused.

Send a test email

Open Send in the endpoint bar and pick Send test email. A sample message with a code and a link is delivered straight to the endpoint, so you can see every part of the email view before wiring up a real sender. It counts as one request. It does not travel over SMTP, so the sender checks (SPF, DKIM, DMARC) do not apply to it, and the dashboard says so.

In the dashboard

Emails show up in the request list with an EMAIL badge, their subject, the sender, the tag, the number of attachments, and the size. Above the list, switch between All, HTTP and Email.

Selecting an email opens its own view:

• Envelope: subject, sender, recipients (with the tag highlighted), when it arrived and its size.
• Sender checks: one badge each for SPF, DKIM, DMARC and TLS.
• Found in this email: the one-time code and the main link, each with a copy button (see below).
• Tabs: Preview (when the email has HTML), Text, Headers, Attachments (when there are any), Authentication, and Raw.
• Download .eml: saves the original message, when it was stored in full.

Notes, pinning, compare, export, search, and live updates work for emails the same way as for HTTP requests.

The preview

The HTML is shown in a sandboxed frame on a white sheet, the way a mail client would show it:

• No scripts run, and forms cannot be submitted.
• Links in the preview do not open. Copy them from Found in this email or the Text tab.
• Remote images are blocked until you click Load images, because loading them tells the sender that the email was opened, and from which IP address. Images written into the HTML as data: URLs show right away. Images attached to the message (cid: references) show as broken, because attachment contents are not kept.
• Switch between a desktop and a mobile width to check a responsive layout.

Codes and links

For signup and login tests, the code or link is usually all you need. The dashboard picks out:

• Codes: 4 to 8 digits (also split in two, like 123 456) or a short mix of letters and digits, but only when a word such as "code", "verification", "PIN" or "sign in" sits next to it. Order numbers, prices, years and phone numbers stay out.
• Links: links that look like the thing the email asks you to click (confirm, verify, reset, sign in, accept an invite) come first. Unsubscribe, preference, tracking and social links are left out.

This runs in your browser when you open an email; nothing extra is stored. To hide it for an endpoint, for example one that receives mail you would rather not have scanned, open Settings, then Receiving, and turn off Show codes and links found in emails.

Authentication

The Authentication tab explains each check our mail server ran when the message arrived:

Failing a check does not stop a message from being captured. The results are there so you can see what a real inbox provider would think of your mail before you ship it.

What is stored

Emails follow the same retention as HTTP requests on your plan.

Quota and limits

An email counts as one request against the same quota as your webhooks, once per endpoint it is addressed to. The account page shows how much of your usage was email.

Messages are accepted or refused while the sender is still connected, so a sender always learns what happened:

A message the sender retries after a temporary failure is captured once, not once per attempt. Sending the same message again on purpose captures it again.

mailhooks.cc only receives. It never sends mail, replies, or bounces of its own.

Notifications

A notification URL fires for emails too. The payload has "method": "EMAIL", the recipient address as path, and the subject followed by the start of the text as preview.

In the API

The REST API returns emails alongside HTTP requests. An email has method set to EMAIL, path set to the recipient address, kind set to email, the full original message (or its headers, for messages over 1 MB) as body, and the parsed message as email.