How do I connect raw MIME webhook to nofeb?
- Copy
inbound.webhook_urls.rawfromGET /v1/me. - POST the message bytes as the body, with
to(comma-separated envelope recipients) and optionallyfromas query parameters. - Treat any 2xx as stored; retry anything else. Redelivering the same message is safe.
- For a one-off import into a single inbox with an API key, use
POST /v1/inboxes/{inbox_id}/inboundinstead.
curl -X POST "https://api.nofeb.com/v1/inbound/raw/$NOFEB_INBOUND_TOKEN?to=support@agents.example.com&from=dana@example.org" \
-H 'content-type: message/rfc822' \
--data-binary @message.eml
# Rotate the token: every earlier one stops working
curl -X POST https://api.nofeb.com/v1/inbound-token/rotate -H "Authorization: Bearer $NOFEB_ORG_KEY" How does the agent get the message?
The same three ways as any other inbound mail. Subscribe a webhook to message.received, pull the event feed, or block on wait_for_email until it arrives:
curl -X POST https://api.nofeb.com/v1/inboxes \
-H "Authorization: Bearer $NOFEB_API_KEY" -H 'content-type: application/json' \
-d '{"local_part": "signup-bot", "ttl_seconds": 3600}'
curl "https://api.nofeb.com/v1/inboxes/$INBOX_ID/wait?has_otp=true&timeout=60" \
-H "Authorization: Bearer $NOFEB_API_KEY"
# → { "message": { "subject": "Your code", "otps": [{ "code": "482913", "source": "body" }], … } } What does nofeb add to a raw message?
- A generic, documented path for anything without a dedicated adapter: Postfix pipes, procmail, cron jobs or a provider not listed here.
- The same pipeline as every other path: envelope routing, inbound hooks, threading, extraction and message.received.
- Messages up to 40 MB are accepted.
Frequently asked questions
How is the raw endpoint authenticated?
By your organization's inbound token in the URL. It can deliver only to your inboxes and verified domains, and rotating it invalidates every earlier token immediately.
What if I omit the to parameter?
nofeb uses the To and Cc headers. Pass the envelope recipients when you have them: they are what the sending server actually addressed, and Bcc recipients only appear there.
Can I import an existing mailbox this way?
Yes. POST each message; redelivering one is harmless. For a single inbox, the authenticated push endpoint takes the same raw message with an API key instead of the token.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Inbound from the provider you already use | Receive through Cloudflare Email Routing with an Email Worker on your own zone, a Postmark inbound stream, a Mailgun route, SendGrid Inbound Parse, or any service that can POST a raw message. Each path is authenticated by your organization's inbound token, which you can rotate at any time, and delivers only to your own inboxes and verified domains. | Shipped |
| Inbound routed by envelope recipient | Mail is delivered to the inbox named in the SMTP envelope, not the To: header, whichever way it arrives, and redelivery is idempotent. | Shipped |
| Reply extraction | Each message carries its new text with quoted history and signature removed. | Shipped |
| safe_body for untrusted mail | The message's new text with zero-width and direction-altering characters, hidden HTML and forgeable quoted history removed, wrapped in a provenance header that tells the model whose words these are. | Shipped |
| One-time code and link extraction | Verification codes and classified links are pulled out of every message and returned as fields. | Shipped |
| Attachment text | Attachments are listed with their extracted text and can be downloaded byte-exact. | Shipped |
| Wait for an email | Long-poll an inbox for up to a minute until a message matching sender, subject or has-a-code arrives. | Shipped |
| Signed webhooks with required scope | Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. | Shipped |
| HTTPS hooks in the pipeline | Signed HTTPS callouts that change what happens: create or reject an inbox for an unknown recipient, accept, reject or quarantine a message before delivery, and allow, deny or hold a send, each with a timeout and a fail-open or fail-closed mode. | Shipped |