> ## Documentation Index
> Fetch the complete documentation index at: https://docs.manypi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List sending inboxes

> Every connected sending identity with its health: today's sends versus the warmup-aware cap, 14-day delivered/failed/opened/bounced, a rolling 24-hour bounce rate, whether the bounce guard has paused it, and a 0–100 health score.

Use an inbox `id` as `smtp_config_id` when creating a campaign or sending.

Requires the `read` permission.



## OpenAPI

````yaml GET /api/outreach/inboxes
openapi: 3.1.0
info:
  title: ManyPI API
  description: >-
    The REST API behind ManyPI — AI lead generation, email validation,
    cold-email outreach, agent runs and web scraping. Every endpoint is
    authenticated with a ManyPI API key (`mpi_...`) or an OAuth 2.1 access
    token, and honours the permissions granted to that credential.
  version: 2.0.0
  contact:
    name: ManyPI Support
    email: support@manypi.com
    url: https://manypi.com
servers:
  - url: https://app.manypi.com
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Leads
    description: Find, store, enrich and manage leads.
  - name: Email validation
    description: Verify that lead addresses can receive mail.
  - name: Outreach
    description: Inboxes, sequences, campaigns, sending and replies.
  - name: Agent
    description: Agent runs, replies and skills.
  - name: Scraping
    description: Scrapers, runs and extracted data.
  - name: Endpoints
    description: Publish scrapers as typed REST endpoints.
  - name: Account
    description: Key validation and account information.
paths:
  /api/outreach/inboxes:
    get:
      tags:
        - Outreach
      summary: List sending inboxes
      description: >-
        Every connected sending identity with its health: today's sends versus
        the warmup-aware cap, 14-day delivered/failed/opened/bounced, a rolling
        24-hour bounce rate, whether the bounce guard has paused it, and a 0–100
        health score.


        Use an inbox `id` as `smtp_config_id` when creating a campaign or
        sending.


        Requires the `read` permission.
      operationId: listInboxes
      parameters:
        - name: brand
          in: query
          description: '`all` reports every inbox in the workspace.'
          schema:
            type: string
      responses:
        '200':
          description: Inboxes with health.
          content:
            application/json:
              schema:
                type: object
                properties:
                  inboxes:
                    type: array
                    items:
                      $ref: '#/components/schemas/Inbox'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    Inbox:
      type: object
      properties:
        id:
          type: string
          format: uuid
          description: Use as `smtp_config_id`.
        name:
          type: string
        from_email:
          type: string
          format: email
        sentToday:
          type: integer
        capToday:
          type: integer
          description: Warmup-aware cap, not the raw daily limit.
        sent14d:
          type: integer
        failed14d:
          type: integer
        opened14d:
          type: integer
        bounced14d:
          type: integer
        bounceRate24h:
          type: number
        warmup_enabled:
          type: boolean
        sending_paused_at:
          type: string
          format: date-time
          nullable: true
          description: Set when the bounce guard paused the inbox.
        sending_paused_reason:
          type: string
          nullable: true
        health:
          type: integer
          minimum: 0
          maximum: 100
    Error:
      type: object
      properties:
        error:
          type: string
          description: Human-readable message.
        code:
          type: string
          description: >-
            A machine-readable code on gated failures: `lead_limit`,
            `outreach_locked`, `validation_credits_exhausted`.
  responses:
    Unauthorized:
      description: >-
        Missing, invalid or expired credential — or a key that lacks the
        permission this route requires.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        A ManyPI API key (`mpi_...`) from Settings → API keys, or an OAuth 2.1
        access token obtained through the MCP consent flow.

````