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

# List all received faxes

> Retrieve every received fax available to the authenticated account.

Retrieve received faxes across the authenticated account. Use `limit` and `cursor` to page through the results.

Each fax includes its job identifier, sender and receiver, duration, page count, and received time.


## OpenAPI

````yaml GET /v1/faxes/all/received
openapi: 3.1.0
info:
  title: Amplify Customer API
  version: 1.0.0
  description: |-
    Canonical contract for the Amplify customer-facing API. This YAML file is
    the source of truth for Postman and Mintlify. Operations marked with
    x-amplify-validation-status: pending were migrated from the legacy Postman
    collection and must be validated before their contract is considered final.
servers:
  - url: https://api.amplify.xyz
    description: Production
  - url: https://dev-api.amplify.xyz
    description: Development
security: []
tags:
  - name: Authentication
  - name: Fax
  - name: Send Faxes
  - name: Receive Faxes
  - name: Manage Faxes
  - name: Workspace
  - name: Numbers
  - name: Contacts
  - name: Documents
  - name: Templates
paths:
  /v1/faxes/all/received:
    get:
      tags:
        - Receive Faxes
      summary: List all received faxes
      description: Returns all received faxes available to the authenticated account.
      operationId: getv1FaxesAllReceived
      parameters:
        - name: limit
          in: query
          required: false
          description: Maximum number of received faxes to return.
          schema:
            type: integer
          example: 20
        - name: cursor
          in: query
          required: false
          description: Cursor used to request another page of results.
          schema:
            type: string
      responses:
        '200':
          description: Received faxes retrieved successfully.
          content:
            application/json:
              schema:
                type: object
                required:
                  - status
                  - message
                  - data
                  - meta
                properties:
                  status:
                    type: integer
                  message:
                    type: string
                  data:
                    type: array
                    items:
                      type: object
                      required:
                        - job_id
                        - receiver
                        - duration
                        - pages
                        - received_time
                        - sender
                      properties:
                        job_id:
                          type: string
                        receiver:
                          type: string
                        duration:
                          type: integer
                        pages:
                          type: integer
                        received_time:
                          type: string
                          description: >-
                            Date and time returned by the current API
                            implementation.
                        sender:
                          type: string
                  meta:
                    type: object
                    required:
                      - total
                      - next_cursor
                      - previous_cursor
                      - limit
                    properties:
                      total:
                        type: integer
                      next_cursor:
                        type: string
                      previous_cursor:
                        type: string
                      limit:
                        type: integer
              example:
                status: 1
                message: Faxes list retrieved successfully
                data:
                  - job_id: 01M1NSBBDF17FJZX9VRPPF635K
                    receiver: '+14084132233'
                    duration: 19
                    pages: 1
                    received_time: '2026-09-04 16:42:46'
                    sender: '+19073131400'
                  - job_id: 01M1NQ8THA0QA42W6TS4Q7SY6D
                    receiver: '+14084132233'
                    duration: 23
                    pages: 2
                    received_time: '2026-09-04 16:06:26'
                    sender: '+19073131400'
                meta:
                  total: 17
                  next_cursor: ''
                  previous_cursor: ''
                  limit: 20
        '500':
          description: The supplied Bearer token could not be parsed.
          content:
            application/json:
              schema:
                type: object
                required:
                  - status
                  - message
                  - data
                properties:
                  status:
                    type: integer
                  message:
                    type: string
                  data:
                    type: string
              example:
                status: 422
                message: UNPROCESSABLE_ENTITY
                data: Invalid token format
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

````