socket.help

An inbox your agent can read.Email webhook forwarding

An owned address for any sign-up, verification or application test flow. Read messages, codes and links in one place.

Loading your workspace…

About Email webhook forwarding

Create an owned address for your agent on socketspace.xyz. Use it to sign up to the app you are testing, then read the message here or let your AI agent wait for it. One-time codes and verification links are extracted automatically.

When to use it

Let your own application react when an owned agent inbox receives a message.

Email webhook forwarding example
PUT /api/email-inboxes/{id}/forwarding
{ "url": "https://your-app.example/hooks/email" }

Your endpoint receives email.received with the structured message; inspect inbox metadata for the latest delivery result.

How to use it

  1. Sign in and choose a 1–7 day lifetime on Free, or an optional custom name on Pro or Team.
  2. Use the address to sign up, reset a password or receive any test email.
  3. Copy the extracted code or open the verification link, or call wait_for_email from your agent.

Limits & privacy

An account is required. Free includes one random address for 1–7 days, default 3. Pro includes 10 and Team 50 addresses that remain active while subscribed. Upgrade before Free expiry to keep the same address. Lapsed paid inboxes pause immediately and are deleted after 30 days; explicit downgrades keep the newest inbox for 7 days. Retired addresses are never reused. Each inbox keeps up to 100 messages; text and HTML are stored up to 64 KiB each and owned inboxes store attachment contents, with a 5 MiB message limit and 25 MiB of attachments per inbox. Download links expire after two minutes. Attachment bytes count against workspace storage and are removed with messages or inbox expiry; files are always untrusted downloads. Outbound email is available only when the operator enables a separate mail relay, with verified Free ownership and per-plan sending caps. Workspace access is required for new inboxes. Forwarding to a public webhook requires Pro or Team, stops when the paid plan lapses, and makes one best-effort delivery attempt per received message.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.