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

# List SMS Conversations

> Get the conversation threads for one of your phone numbers.

Returns one entry per other party that the number has texted with,
each carrying the most recent message — useful for showing an inbox
with a preview of the last message in each thread.

Scoped to ``user_id``: only that user's own messages on the number are
shown, so a reassigned number never leaks another user's threads. Works
even after the number is deleted — the user keeps seeing past conversations.



## OpenAPI

````yaml GET /v1/platform/phone-numbers/sms/messages/conversations
openapi: 3.1.0
info:
  title: Finogate Platform API v1
  version: 0.1.0
servers:
  - url: https://api-sandbox.finogates.com
    description: Sandbox
  - url: https://api.finogates.com
    description: Production
security: []
tags:
  - name: auth
  - name: users
  - name: payees
  - name: verification
  - name: bank accounts
  - name: card processing
  - name: digital-assets
  - name: international
  - name: onboarding
  - name: pending-applications
  - name: wallets
  - name: payments
  - name: catalog
  - name: webhooks
  - name: phone-numbers
  - name: sms
  - name: calls
  - name: listings
  - name: embed-tokens
paths:
  /v1/platform/phone-numbers/sms/messages/conversations:
    get:
      tags:
        - sms
      summary: List SMS Conversations
      description: >-
        Get the conversation threads for one of your phone numbers.


        Returns one entry per other party that the number has texted with,

        each carrying the most recent message — useful for showing an inbox

        with a preview of the last message in each thread.


        Scoped to ``user_id``: only that user's own messages on the number are

        shown, so a reassigned number never leaks another user's threads. Works

        even after the number is deleted — the user keeps seeing past
        conversations.
      operationId: >-
        list_phone_sms_conversations_v1_platform_phone_numbers_sms_messages_conversations_get
      parameters:
        - name: number
          in: query
          required: true
          schema:
            type: string
            description: The phone number whose conversation threads to list.
            title: Number
          description: The phone number whose conversation threads to list.
        - name: user_id
          in: query
          required: true
          schema:
            type: string
            description: >-
              The user whose messages on the number are listed (works even if
              the number was later deleted or reassigned).
            title: User Id
          description: >-
            The user whose messages on the number are listed (works even if the
            number was later deleted or reassigned).
        - name: limit
          in: query
          required: false
          schema:
            type: integer
            maximum: 200
            minimum: 1
            description: How many conversations to return per page (1 to 200).
            default: 50
            title: Limit
          description: How many conversations to return per page (1 to 200).
        - name: offset
          in: query
          required: false
          schema:
            type: integer
            minimum: 0
            description: How many conversations to skip before this page starts.
            default: 0
            title: Offset
          description: How many conversations to skip before this page starts.
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - _AuthenticatedBearer: []
components:
  schemas:
    ListResponse:
      properties:
        status_code:
          type: integer
          title: Status Code
          description: HTTP status code for the response.
        data:
          title: Data
          description: Payload or error details.
        query_generated_time:
          type: integer
          title: Query Generated Time
          description: >-
            UTC timestamp (milliseconds since epoch) when response was
            generated.
        row_count:
          type: integer
          minimum: 0
          title: Row Count
          description: Total rows matching the request filters (not just this page).
        limit:
          anyOf:
            - type: integer
              minimum: 1
            - type: 'null'
          title: Limit
          description: >-
            Page size used for this response. Null for cursor-paginated
            endpoints.
        current_page:
          anyOf:
            - type: integer
              minimum: 1
            - type: 'null'
          title: Current Page
          description: >-
            1-indexed page number for this response. Null for cursor-paginated
            endpoints.
        total_page_number:
          anyOf:
            - type: integer
              minimum: 0
            - type: 'null'
          title: Total Page Number
          description: >-
            Total number of pages given the current limit. Null for
            cursor-paginated endpoints.
        next_cursor:
          anyOf:
            - type: string
            - type: 'null'
          title: Next Cursor
          description: Cursor for the next page, if available.
      type: object
      required:
        - status_code
        - data
        - query_generated_time
        - row_count
      title: ListResponse
      description: |-
        Standard response wrapper for list responses.

        Declare ``ListResponse[list[SomeModel]]`` to render the real ``data``
        array schema in OpenAPI/Swagger; a bare ``ListResponse`` leaves ``data``
        untyped.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    _AuthenticatedBearer:
      type: oauth2
      flows:
        password:
          scopes: {}
          tokenUrl: /v1/platform/auth/token

````