Inboxes and forwarding

When you create an inbox, its address is built from the name you give it plus a short random suffix, so it cannot be guessed:

Name "Orders"            [email protected]
Name "AP invoices EU"    [email protected]

Plus tags route to the same inbox, with the same schema and the same limits as the plain address. Use them to tell sources apart without new inboxes: the address the email was sent to, tag included, comes back in the to field of every result, so your code or automation can route on it:

[email protected]
[email protected]

# in the result
"to": "[email protected]"

Each inbox has one schema, an optional list of allowed senders, an attachments switch and an optional review threshold. Starter includes 5 inboxes, Growth 25 and Scale unlimited. Deleting an inbox does not give back the emails it already used this period. Create inboxes in the dashboard or with POST /v1/inboxes from the API reference.

1. In Gmail open Settings, See all settings, Forwarding and POP/IMAP, and choose Add a forwarding address. Enter the inbox address.
2. Gmail sends a forwarding confirmation email to that address. It shows up in the inbox log in ParsedMail with status skipped. Open it there and click the confirmation link, or copy the confirmation code into Gmail.
3. Create a filter, for example from:[email protected], and choose Forward it to the inbox address.

Forwarding confirmation emails are never parsed and never counted toward your plan. They also pass an allowed senders list, so you can confirm forwarding before or after you restrict senders.

1. In Outlook create a rule (Settings, Mail, Rules) with a condition such as From or Subject includes.
2. Set the action to Forward to, or Redirect to, the inbox address.

Microsoft 365 blocks automatic forwarding to external addresses by default. If forwarded mail never arrives, ask your admin to allow external forwarding for the mailbox in the outbound spam filter policy of Microsoft 365 Defender. A redirect keeps the original sender in the From header, which helps allowed senders and duplicate detection. Some Outlook setups also send a confirmation email; like the Gmail one, it lands in the log with status skipped and is not counted.

On your own mail server, add the inbox address as an alias target or a BCC copy of a mailbox, for example in a Postfix virtual map:

[email protected]    [email protected], [email protected]

Emails that already sit in your application can skip mail entirely. POST them to /v1/inboxes/{id}/emails as raw MIME or JSON, as described in sending emails to the API. One message can be up to 25 MB including attachments.

An inbox accepts mail from anyone who knows the address until you add allowed senders. Enter one rule per line:

[email protected]
@northwind-supply.example
contoso.example

A full address must match exactly, @domain and a bare domain match any address at that domain. Mail from other senders is stored with status blocked_sender, not parsed and not counted. Matching uses the From address of the email, so when you forward manually from your own mailbox, add your own address or use a redirect rule.

Pausing an inbox stops parsing without losing forwarded mail. Emails that arrive by mail while it is paused are stored with status failed and the message "The inbox is paused or deleted", are not counted, and can be replayed after you resume it. The API refuses new emails for a paused inbox with 409 inbox_paused, so your code can keep them and retry later.

On Scale you can receive on a subdomain of your own, so suppliers see your brand. In Settings enter a domain such as in.yourcompany.com, then add an MX record at your DNS host:

in.yourcompany.com.   MX   10   inbound.parsedmail.com.

Mail to an inbox name at your domain then reaches that inbox. The part before the @ is the inbox name including its suffix, so the inbox [email protected] also receives at [email protected], and plus tags work the same way. Use a subdomain that has no other mail on it, because the MX record sends all of its mail to ParsedMail.

On Growth and Scale one inbox can hold several kinds of email. Switch on classification and pick candidate schemas, for example Invoice, Order confirmation and Shipping notice. The schema attached to the inbox is always one of the candidates, and you need at least two in total. For each email the model picks the schema that fits and the result says which:

"classification": {"schema": "sch_2hd9wq1kz0", "name": "Order confirmation", "confidence": 0.93}

When no candidate fits, classification.schema is null and the email goes to the review queue. Schema descriptions help the choice, so describe each one in a sentence; see schema best practices.

On Growth and Scale an email goes to the review queue with status needs_review when its confidence_avg is below the threshold, when a required field is missing, or when classification found no schema. The workspace default is 0.80 and each inbox can override it with a value from 0 to 1. A reviewer sees the original email next to the values, corrects them and approves, which sends the corrected values to your webhook, or rejects the email, which sets status failed. On Starter there is no review queue and every parsed email is delivered with its confidence scores.