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

# List a customer's verification receipts

> Audit listing of the customer's contact-verification attempts, newest first. Targets are masked.



## OpenAPI

````yaml /openapi/customer-20260203.json get /accounts/customers/{customerId}/verifications
openapi: 3.1.0
info:
  title: CUSTOMER
  termsOfService: urn:tos
  license:
    name: Apache 2.0
    url: https://springdoc.org
  version: '2026-02-03'
  description: ''
servers:
  - url: https://api-sb.meld.io
    description: Meld API sandbox
  - url: https://api.meld.io
    description: Meld API production
security: []
tags:
  - name: Virtual Account
    description: ''
  - name: Customers
paths:
  /accounts/customers/{customerId}/verifications:
    get:
      tags:
        - Customers
      summary: List a customer's verification receipts
      description: >-
        Audit listing of the customer's contact-verification attempts, newest
        first. Targets are masked.
      operationId: accounts-customers-verifications-search
      parameters:
        - name: Meld-Version
          in: header
          description: Dated API version to use for this request, e.g. `2026-02-03`.
          required: false
          schema:
            type: string
            example: '2026-02-03'
        - name: customerId
          in: path
          description: Customer id
          required: true
          schema:
            type: string
        - name: channel
          in: query
          description: Contact channel
          required: false
          schema:
            type: string
            enum:
              - EMAIL
              - PHONE
        - name: status
          in: query
          description: Verification status
          required: false
          schema:
            type: string
            enum:
              - PENDING
              - VERIFIED
              - EXPIRED
              - FAILED
              - INVALIDATED
      responses:
        '200':
          description: Verifications are returned
          content:
            '*/*':
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/VerificationResponse'
        '400':
          description: 'Bad Request : check request values and format'
        '401':
          description: Invalid credentials
        '403':
          description: Unauthenticated or authenticated with insufficient access
        '404':
          description: Customer cannot be found
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: >-
            Server Error. This applies to all 5xx errors, including but not
            limited to 500, 501, 502, 503, and 504 errors. You should treat all
            of these errors the same.
      security:
        - ApiKeyAuth: []
components:
  schemas:
    VerificationResponse:
      type: object
      description: State of a contact verification
      properties:
        channel:
          type: string
          description: Contact channel
          enum:
            - EMAIL
            - PHONE
        expiresAt:
          type: string
          description: When the code expires (ISO-8601)
        resendAvailableAt:
          type: string
          description: When a new code can be requested (ISO-8601)
        status:
          type: string
          description: Verification status
          enum:
            - PENDING
            - VERIFIED
            - EXPIRED
            - FAILED
            - INVALIDATED
        target:
          type: string
          description: Masked contact value the code was sent to
          example: j•••@example.com
        verificationId:
          type: string
          description: Verification id
    ErrorResponse:
      type: object
      properties:
        code:
          type: string
          description: Stable identifier for the failure.
        errors:
          type: array
          items:
            type: string
          description: What was rejected, one entry per field or rule.
        message:
          type: string
          description: A description of what went wrong.
        requestId:
          type: string
          description: Quote this when asking Meld about a specific failure.
        serviceProviderDetails:
          type: object
          properties:
            code:
              type: string
              description: The provider's own error code, when it sent one.
            message:
              type: string
              description: The provider's own message.
          example:
            code: '5034'
            message: >-
              Digital currency and blockchain combination is restricted for
              customer's country
          description: >-
            The provider's own error detail, when the failure came from a
            service provider. Usually `code` and `message`; a few providers pass
            their own body through, so other keys can appear.
          additionalProperties: {}
        timestamp:
          type: string
          format: date-time
          description: >-
            When the failure occurred. ISO 8601, UTC
            (`YYYY-MM-DDThh:mm:ss.sss+00:00`).
          example: '2026-08-14T09:41:22.482+00:00'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      x-default: BASIC <Meld API Key>

````