Forward your OTPs to anywhere

Working in a client’s inbox? Share verification codes with the client as another otp1 user — no screenshots, no copy-paste.

Help a parent or relative with banking, government, or subscription logins. The OTP lands in your own inbox.

Wire OTP delivery into a downstream service that doesn’t speak email. Programmatic, low-latency, with signed webhook payloads.

Forward a few OTPs a week from multiple email accounts to yourself across devices. Mobile-friendly in-app inbox, nothing to install.

Point a mail filter at your forwarding address (one per inbox — Gmail, Outlook, bank alerts, etc.).

Choose where the OTPs go: Discord, Slack, an email link, a webhook, or your own code via the API.

Within seconds of the original email arriving, the OTP shows up wherever you chose — labeled by source.

Your OTP, always. Real-time SSE push, 7-day retention, source-labeled. The system’s source of truth — not a destination you can turn off.

A short-lived, opaque link that opens the OTP in a browser. Share it with someone you trust. Free is link-only; paid plans can include the plaintext in the body.

A formatted embed — source label, OTP, timestamp — posted to a webhook in the channel you choose.

A Block Kit message with the OTP front and center, posted to a Slack incoming webhook.

A signed JSON payload (HMAC-SHA256) to a URL you own. Source email, source label, OTP, and a unique event id — everything an automation needs.

Hand the OTP to someone else on otp1.me. The recipient sees it in their own in-app inbox, labeled with your source and a “Shared” badge.

Emails and OTPs are purged on a rolling sweep. You can shorten or lengthen the window per plan — we don’t keep anything you don’t need.

Your mail-client filter is the single source of truth. We don’t run subject-keyword or sender-allowlist filters on inbound mail — nothing is silently dropped on our end.

Destination configs (webhook URLs, secrets, etc.) are encrypted with AES-256-GCM. Webhook signing secrets are stored hashed — we can’t read them, and neither can anyone who breaches the DB.

We keep the OTP and a few metadata fields — not the full email body. We are an OTP service, not an email archive.

From the address you want to log in with, send anything to signup@otp1.me. The from-address becomes your identity — no password, no card, no app install.

We send a one-tap login link back. You land in your in-app inbox. Inbound email proves the address is yours, so there’s no separate verification step.

Point a mail filter at your forwarding address and pick where the OTPs go. First OTP typically arrives in under a minute.