Forward Emails to your Webhook

How does this work?

You register a URL with hookup.email and in return get an email address. Any email arriving at this mailbox will be forwarded to the registered web address via an HTTP POST request. The entire email, including headers, is sent unmodified as it arrives.

Fault tolerance: Your server must respond with a 2xx status code to signal success or mail delivery will be retried with increasing delay for ~24 hours.

Authentication: You can include basic auth credentials in the URL to authenticate against the server: https://user:pass@web.site/webhook.

Channel routing: Have your emails be sent to your hookup address and add a channel name, for example, x5dc5F+marketing@hookup.email, and the email will be delivered together with the HTTP header x-hookup-channel: marketing. That way you can route incoming mail to different business logics.

How to create a hookup?

Send an email to lets@hookup.email with only your URL as content, e.g, https://web.site/webhook. You'll receive a response with the email address for your hookup.

What does it cost?

Nothing. But there's currently a limit of 500 monthly processed mails per hookup address.

No passwords?

No. All communcation happens through email and only you (should) have control over your mailbox.

Abuse prevention

Upon creating a hookup you'll receive instructions on how to verify the domain of the URL. hookup.email will not willy-nilly bomb any web address. But beware: After domain ownership verification all limits are off - there's no rate limit and any amount of mail at any point in time will be sent to your server.

What about privacy?

If operational security is your biggest concern, you should not use any 3rd party service — including this one. That said, hookup.email does not permanently store any received email. All processing happens in real time, data stays in memory until the URL was called.

About data protection and privacy

hookup.email permanently stores the following and only the following of your data for purposes of service fulfillment:

• A cryptographic hash of the email that creates a hookup
• The web URL
• Usage statistics (number of processed mails per hookup)

Additionally, any email passing through the hookup.email systems will be processed for the purpose of dispatching incoming mail to the correct URL and can potentially be seen and read by the service operators.

Your data will be permanently deleted after all hookups registered with your email address have not received any traffic for 30 days. As your account's mail address is not stored in clear text there will be no notification whatsoever before account deletion.

Now tell me how it is made

hookup.email is written in Elixir. Among other things it contains this site and an SMTP server built on top of the wonderful gen_smtp Erlang library. It further leverages the mailing infrastructure of bubble.email. The server filesystem is fully encrypted.