MultiMail Oversight API

The Oversight API from MultiMail — 2 operation(s) for oversight.

GitHub OpenAPI

Operations 2

GET /v1/oversight/pending List emails pending oversight approval #
POST /v1/oversight/decide Approve or reject a pending email #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/multimail-dev:multimail-dev-oversight-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

multimail-dev-oversight-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: MultiMail Oversight API
  version: 2.0.0
  description: Email-as-a-Service for AI agents. Inbound email converted to markdown, outbound markdown converted to HTML. Built on Cloudflare Workers.
servers:
- url: https://api.multimail.dev
tags:
- name: Oversight
paths:
  /v1/oversight/pending:
    get:
      summary: List emails pending oversight approval
      description: Requires oversight scope.
      security:
      - bearerAuth: []
      responses:
        '200':
          description: Pending emails
          content:
            application/json:
              schema:
                type: object
                properties:
                  emails:
                    type: array
                    items:
                      type: object
                      properties:
                        id:
                          type: string
                        mailbox_id:
                          type: string
                        direction:
                          type: string
                          enum:
                          - inbound
                          - outbound
                        from:
                          type: string
                        to:
                          type: array
                          items:
                            type: string
                        subject:
                          type: string
                        body_markdown:
                          type: string
                        status:
                          type: string
                        received_at:
                          type: string
                          format: date-time
      tags:
      - Oversight
      operationId: getV1OversightPending
      x-operation-id-source: derived
  /v1/oversight/decide:
    post:
      parameters:
      - name: X-MultiMail-Approval-Code
        in: header
        required: false
        schema:
          type: string
        description: Operator-delivered single-use proof for the exact request. Without proof, HTTP 202 requests operator approval and does not complete the operation. Confirmation booleans and MCP UI hints cannot grant authority.
      summary: Approve or reject a pending email
      description: Requires oversight scope. Approved outbound emails are sent immediately. Sensitive changes require a request-bound operator code; API-key scope alone does not authorize them.
      security:
      - bearerAuth: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              required:
              - email_id
              - action
              properties:
                email_id:
                  type: string
                action:
                  type: string
                  enum:
                  - approve
                  - reject
      responses:
        '200':
          description: Decision applied
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                    - approved
                    - approved_and_sent
                    - rejected
                  postmark_message_id:
                    type: string
        '202':
          description: Operator approval requested; operation not completed
        '404':
          description: Email not found
      tags:
      - Oversight
      operationId: postV1OversightDecide
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: 'API key (mm_live_...). Keys have scopes: read (list/read emails, mailboxes, contacts), send (send/reply/cancel emails), admin (manage mailboxes, API keys, billing, account), oversight (approve/reject pending emails).'