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

# List Flow responses

> The forms customers submitted to ONE Flow, newest first. The Flow is resolved inside the key's own WABA first, and that resolution is the only thing that scopes what follows — a Flow of another WABA (including another WABA of the same tenant) answers 404 and no response is ever read.

Responses past their retention window are excluded HERE, not only by the pruning job, so a caller can never read a submission the published window says is gone. `contactPhone` is `null` when the phone is no longer ours to publish. `externalMessageId` is Meta's `wamid` and is named as a provider id on purpose — every other id on this surface is local.

`notice: "FLOW_RESPONSES_WINDOW_TRUNCATED"` appears on the page when the Flow minted more sends than one request will correlate (a 10,000-session ceiling). A short answer that does not say it is short is what makes a caller conclude submissions were lost. Permission `flows:read`.

**Requires a number-scoped key.** A tenant-scoped key must name the number with the `x-whatsapp-number-id` header, or it gets 403 `TENANT_SCOPE_NOT_ALLOWED`.



## OpenAPI

````yaml openapi.json GET /v1/flows/{id}/responses
openapi: 3.1.0
info:
  title: Pilot Status API
  version: 1.0.0
  license:
    name: Pilot Status Terms of Service
    url: https://pilotstatus.com.br/terms
  description: >-
    Public REST API for Pilot Status. Authenticate with the `x-api-key: ps_...`
    header (or `x-api-key-id`). Base URL: https://pilotstatus.com.br
servers:
  - url: https://pilotstatus.com.br
security:
  - apiKey: []
  - apiKeyId: []
paths:
  /v1/flows/{id}/responses:
    get:
      tags:
        - Flows
      summary: List Flow responses
      description: >-
        The forms customers submitted to ONE Flow, newest first. The Flow is
        resolved inside the key's own WABA first, and that resolution is the
        only thing that scopes what follows — a Flow of another WABA (including
        another WABA of the same tenant) answers 404 and no response is ever
        read.


        Responses past their retention window are excluded HERE, not only by the
        pruning job, so a caller can never read a submission the published
        window says is gone. `contactPhone` is `null` when the phone is no
        longer ours to publish. `externalMessageId` is Meta's `wamid` and is
        named as a provider id on purpose — every other id on this surface is
        local.


        `notice: "FLOW_RESPONSES_WINDOW_TRUNCATED"` appears on the page when the
        Flow minted more sends than one request will correlate (a 10,000-session
        ceiling). A short answer that does not say it is short is what makes a
        caller conclude submissions were lost. Permission `flows:read`.


        **Requires a number-scoped key.** A tenant-scoped key must name the
        number with the `x-whatsapp-number-id` header, or it gets 403
        `TENANT_SCOPE_NOT_ALLOWED`.
      operationId: get_flows_id_responses
      parameters:
        - name: id
          in: path
          required: true
          description: >-
            The **local** id of the Flow — the `id` field `GET /v1/flows`
            returns, never `metaFlowId`.
          schema:
            type: string
          example: cmf1a2b3c4d5e6f7g8h9i0j1
        - name: page
          in: query
          required: false
          description: Page number, 1-based.
          schema:
            type: integer
            minimum: 1
            default: 1
          example: 1
        - name: pageSize
          in: query
          required: false
          description: Rows per page. Default 30, maximum 100.
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 30
          example: 30
      responses:
        '200':
          description: List Flow responses
          content:
            application/json:
              example:
                responses:
                  - id: cmf9z8y7x6w5v4u3t2s1r0q9
                    flowId: cmf1a2b3c4d5e6f7g8h9i0j1
                    contactPhone: '5564999978874'
                    flowToken: b7c1e4f2a9d84c6e8f0a1b2c3d4e5f60
                    externalMessageId: wamid.HBgNNTU2NDk5OTc4ODc0FQIAERgSN0E5...
                    response:
                      screen_0_nome: Amanda
                      screen_0_nota: '9'
                    receivedAt: '2026-09-01T18:22:11.000Z'
                    expiresAt: '2026-10-01T18:22:11.000Z'
                total: 1
                page: 1
                pageSize: 30
                totalPages: 1
        '400':
          description: Pagination too deep (`page` × `pageSize` past the ceiling)
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    description: Portuguese half
                  errorEN:
                    type: string
                    description: English half
                  code:
                    type: string
              example:
                error: >-
                  Paginação profunda demais: page × pageSize não pode passar de
                  10000.
                errorEN: 'Pagination too deep: page × pageSize must not exceed 10000.'
                code: INVALID_PAGINATION
        '401':
          description: Missing or invalid `x-api-key` / `x-api-key-id` header
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
              example:
                error: Unauthorized
        '403':
          description: >-
            Tenant-scoped key used on a number-scoped endpoint, or the key's
            role lacks the permission
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
              example:
                error: Tenant-scoped keys cannot call number endpoints
                code: TENANT_SCOPE_NOT_ALLOWED
        '404':
          description: >-
            No Flow with that id inside the key's own WABA. Never 403: a Flow of
            another tenant is indistinguishable from one that does not exist, on
            purpose — a 403 would confirm someone else's id to whoever guessed
            it
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    description: Portuguese half
                  errorEN:
                    type: string
                    description: English half
                  code:
                    type: string
              example:
                error: Flow não encontrado para o número desta chave.
                errorEN: Flow not found for this key's number.
                code: FLOW_NOT_FOUND
        '422':
          description: >-
            The key's number is not a Meta (Cloud API) number, or has no WABA
            behind it
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    description: Portuguese half
                  errorEN:
                    type: string
                    description: English half
                  code:
                    type: string
              example:
                error: >-
                  Flows existem apenas em números Meta (API Oficial). O número
                  desta chave não é Meta ou não tem uma WABA associada — use uma
                  chave de um número Meta.
                errorEN: >-
                  Flows only exist on Meta (Cloud API) numbers. This key's
                  number is not a Meta number, or has no WABA behind it — use a
                  key bound to a Meta number.
                code: FLOW_REQUIRES_META_NUMBER
        '429':
          description: Rate limit exceeded
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
              example:
                error: Too many requests
        '500':
          description: >-
            Internal error. Never carries the internal message — that belongs in
            the log
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                    description: Portuguese half
                  errorEN:
                    type: string
                    description: English half
                  code:
                    type: string
              example:
                error: Erro interno do servidor.
                errorEN: Internal server error.
                code: INTERNAL_ERROR
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: Your ps_ API key
    apiKeyId:
      type: apiKey
      in: header
      name: x-api-key-id
      description: API key id (alternative to x-api-key)

````