Inbound email → HTTP POST
Turn emails into webhooks.
Anything mailed to your Tempy address is parsed and POSTed to your URL as signed JSON, seconds after it lands — with automatic retries while your endpoint is down.
Free for 5 sender addresses. No credit card, no OAuth, no IMAP.
- Delivered in secondsThe first POST leaves within a second of the email arriving.
- Retried 5 timesAbout 30 s, 1 m, 2 m, 4 m — every attempt shows in your log.
- Signed with HMAC-SHA256Verify the raw body before you trust a single field.
Three steps. No OAuth, no IMAP, no polling.
Get your address
Your permanent inbound email address. Created instantly.
Forward your email
Set up a forwarding rule in Gmail, Outlook, Apple Mail or any SMTP provider.
Receive a webhook
Every incoming email is delivered to your webhook endpoint as JSON.
Set up forwarding in two minutes
Pick your mail provider. No API keys, no passwords shared with us.
Open Gmail settings → See all settings → Forwarding and POP/IMAP.
Click Add a forwarding address and paste your Tempy address.
Confirm the verification email — it appears in your Tempy log within seconds.
Optional: create a filter so only certain emails are forwarded.
Most providers send a confirmation email to your Tempy address first. It shows up in your log — open it and click the confirmation link.
✓Keep a copy of forwarded messages
What your API receives
Parsed sender, subject, text and HTML bodies, headers and attachments — one signed POST per email.
- from, to
- RFC 5322 addresses, parsed
- text, html
- Both bodies, UTF-8
- attachments[]
- Signed URLs, 24 h
- headers{}
- Every original header
{
"id": "em_wnrppxfrp5p9wvv1",
"from": "you@gmail.com",
"to": "inbox_7wgaav5mdb@tempy.uk",
"subject": "Your verification code",
"text": "Your code is 482913",
"html": "<p>Your code is <b>482913</b></p>",
"headers": { "message-id": "<…@mail.gmail.com>" },
"attachments": [],
"received_at": "2026-09-03T10:42:11Z"
}Built for developers
Signed requests
Every request carries an HMAC-SHA256 signature so you can verify it came from us.
Automatic retries
Failed deliveries are retried up to 5 times with exponential backoff.
Delivery logs
Status, response time and the full signed request headers and response for every delivery.
Parsed payload
Clean JSON. Text, HTML, headers and attachments already extracted.
Pricing that counts one thing
The number of unique email addresses forwarding to your endpoint. That's it.
- 1 Tempy address
- 5 unique sender addresses
- Webhook delivery
- Automatic retries
- Basic delivery logs
- Everything in Free
- Each additional unique sender address
- Cancel anytime
- Everything in Free
- Unlimited sender addresses
- One flat price, no surprises
A sender address is any email address that forwards to your Tempy address. Detected automatically — nothing to configure.
Security & reliability
Tempy is a relay, not an inbox.
- 01Email receivedSMTP · TLS
- 02Held in memoryRAM only · no disk
- 03POST to your APIHTTPS · HMAC-SHA256
- 04Deleted≤ 5 attempts · then purge
HTTPS delivery
Webhooks are delivered over TLS only.
Signed requests
Verify every payload with your webhook secret.
Automatic retry
Up to 5 attempts before we mark a delivery failed.
Temporary processing
Emails are held in memory only until delivery completes.
No permanent inbox
We don't store your email after delivery.
No human access
Nobody at Tempy reads email content by default.
Questions
No. You only set up a forwarding rule in your mail client. Tempy never connects to your account.
Point your first email at your own API.
Create an account, copy your Tempy address, add one forwarding rule. The first webhook usually arrives before you have finished reading this page.
One flat price, no surprises
- Free to startFive sender addresses on the free plan, with no card and no trial clock.
- No access to your mailboxYou add a forwarding rule and can delete it just as fast. Tempy never signs in to Gmail or Outlook.
- Nothing kept afterwardsEmail content is purged once delivery finishes. There is no inbox here to breach.