Ingest .eml from Lambda (archive only)
Archive-only ingest. Match recipient against Z_Mailboxes (Delivered-To → X-Original-To → To → Cc). If found → archive into stand-gest:{co}/{pv}/emails/... and insert a Z_EmailMessages row.
No mailbox match → RECORD the drop in Z_EmailIngestDrops and answer 202. Portal-lead emails (Standvirtual / OLX / Carmine / etc.) are owned by Lambda's BE_ENDPOINT → /email/inbound, never this route.
Why 202 and not an error: the deployed SES Lambda's _post_to_archive() swallows every outcome and never raises, so a status code alone changes nothing observable — the durable row is the actual fix. And a 5xx would make the second ingest Lambda retry a permanently unroutable address forever. 202 = "accepted, not routed", which is honest and terminal.
Request
- Base URLhttps://api.multigest.pt (the document declares no server; this is the origin it was published from)
- URLhttps://api.multigest.pt/public/email/inbox-ingest
- AuthAPI key in header x-api-token and API key in header x-origin-verify
Headers
Response
Successful Response
Changes
No recorded changes to this operation across all 21 revisions of this API.