What do I provide?
Route name and a destination webhook URL.
Forward incoming mail at a PicoSvc-issued address to a webhook.
Sign in to create or edit resources. Product details, the demo, and documentation are available without an account.
Developers processing inbound mail as app events.
Create a Hooks inbox, use its URL for a Mail route, send a test email to the issued address, then inspect the JSON in Hooks.
See setup and API examples →Route name and a destination webhook URL.
An [email protected] receiving address, delivery history, and JSON sent to your webhook.
Only a destination webhook URL; you do not need a domain or MX record. PicoSvc Hooks can provide a destination.
1 route · 100 mails
5 routes · 2k mails
25 routes · 20k mails
These limits are a guide. Check the purchase options below for the plan price and billing terms.
These plans are for this service only. Review the price and renewal terms in checkout before you buy.
Loading plans…
Dimension:Receiving address and mail processing
Issue a distinct address per route and relay to a webhook with history.
Documents inbound mail on provided or custom domains, with content and attachment APIs.
Official alternative documentation ↗This compares feature scope, not relative quality, performance, or price. Recheck the linked official source.
Not an inbox UI or sending API. Receiving remains unverified until operator setup and an end-to-end delivery test pass.