> ## Documentation Index
> Fetch the complete documentation index at: https://telnesstech-a0a16404.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# List orders

> List orders with optional filtering and pagination.



## OpenAPI

````yaml /api-reference/bundled_openapi.json get /orders
openapi: 3.1.0
info:
  title: Telness Tech Connect
  version: 2.0.0-alpha
  description: >
    Telness Tech Connect API provides all you need to own your user's
    connectivity experience.


    Go back to [Telnesstech.com](https://telnesstech.com)
servers:
  - url: https://apiv2.example.com
    description: Connect API URL for your domain
security:
  - apiKey: []
  - bearerAuth: []
    apiKey: []
tags:
  - name: Auth
    description: Authenticate users and obtain access tokens.
  - name: Users
    description: Manage users.
  - name: Customers
    description: Manage customers.
  - name: Subscriptions
    description: Manage subscriptions and subscription.
  - name: Subscription Addons
    description: Manage subscription addons.
  - name: Subscription Usage
    description: Get subscription usage.
  - name: Subscribers
    description: Manage subscribers.
  - name: Licenses
    description: Manage licenses.
  - name: Product Offerings
    description: Browse product offerings.
  - name: Product Catalogs
    description: Browse product catalogs.
  - name: Product Discounts
    description: Discounts and promotions.
  - name: Orders
    description: Manage orders and line items.
  - name: Payment Intents
    description: >-
      Inspect payment intents, the money collected over card rails for orders
      and renewals.
  - name: Payment Links
    description: Create and manage payment links for orders and invoices.
  - name: Payment Sessions
    description: Create and manage payment sessions for orders.
  - name: Payment Profiles
    description: Manage customer payment profiles and methods.
  - name: Payment Profile Sessions
    description: Create sessions for setting up payment profiles.
  - name: Signing sessions
    description: Handle contract signing sessions for postpaid orders.
  - name: Porting
    description: Manage number porting for subscriptions.
  - name: Taxes
    description: Calculate taxes for products and line items.
  - name: Invoices
    description: Manage invoices and invoice items.
  - name: Tools
    description: >-
      Tools for address validation, number porting, device info, and network
      coverage.
  - name: Inventory
    description: Manage phone number inventory, SIM cards, and reservations.
  - name: Workflows
    description: Dynamic processing of customer journeys and events.
paths:
  /orders:
    get:
      tags:
        - Orders
      summary: List orders
      description: List orders with optional filtering and pagination.
      operationId: listOrders
      parameters:
        - $ref: '#/components/parameters/Limit'
        - $ref: '#/components/parameters/Cursor'
        - name: state
          in: query
          description: Filter by order state
          schema:
            $ref: '#/components/schemas/OrderState'
        - name: userId
          in: query
          description: Filter by user ID
          schema:
            type: string
        - name: customerId
          in: query
          description: >
            Filter by customer. May be the entity's internal UUID or an external
            reference identifier.

            Reference identifiers MUST be prefixed with `rid_` (e.g.,
            `rid_crm-customer-12345`) so the API

            can distinguish them from internal UUIDs. The prefix is stripped
            before lookup.
          schema:
            type: string
        - name: expiresAfter
          in: query
          description: Filter orders expiring after this date
          schema:
            type: string
            format: date-time
        - name: expiresBefore
          in: query
          description: Filter orders expiring before this date
          schema:
            type: string
            format: date-time
      responses:
        '200':
          description: Orders retrieved successfully
          content:
            application/json:
              schema:
                type: object
                required:
                  - items
                  - pagination
                properties:
                  items:
                    type: array
                    items:
                      $ref: '#/components/schemas/OrderListItem'
                  pagination:
                    $ref: '#/components/schemas/Pagination'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '429':
          $ref: '#/components/responses/TooManyRequests'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  parameters:
    Limit:
      in: query
      name: limit
      schema:
        type: integer
        minimum: 1
        maximum: 1000
        default: 100
      description: The maximum number of items to return.
    Cursor:
      in: query
      name: cursor
      schema:
        type: string
      description: Opaque pagination token from a previous response's nextCursor.
  schemas:
    OrderState:
      type: string
      description: |
        The status of an order in its lifecycle.

        - PENDING: Order is in cart state, can be modified
        - PENDING_PAYMENT: Order is locked and awaiting payment completion
        - SUBMITTED: Order has been submitted for processing
        - PENDING_APPROVAL: Order is pending approval
        - PROCESSING: Order is being fulfilled
        - COMPLETED: Order has been successfully fulfilled
        - CANCELLED: Order was cancelled before completion
        - EXPIRED: Order expired due to inactivity
        - FAILED: Order fulfillment failed
      enum:
        - PENDING
        - PENDING_PAYMENT
        - SUBMITTED
        - PENDING_APPROVAL
        - PROCESSING
        - COMPLETED
        - CANCELLED
        - EXPIRED
        - FAILED
    OrderListItem:
      type: object
      description: Optimized order representation for list operations.
      required:
        - orderId
        - state
        - createdAt
        - updatedAt
      additionalProperties: false
      properties:
        orderId:
          type: string
          description: The unique identifier for the order.
          example: ce0539b4-ec57-4709-b72e-47892586d05a
        state:
          $ref: '#/components/schemas/OrderState'
        customer:
          $ref: '#/components/schemas/EmbeddedCustomer'
        pricing:
          type: object
          description: Summary pricing information for the order.
          required:
            - total
            - currency
          additionalProperties: false
          properties:
            total:
              type: number
              format: decimal
              description: Final order total including all taxes and fees.
            currency:
              type: string
              description: ISO 4217 currency code.
              example: USD
        validationStatus:
          type: string
          enum:
            - VALID
            - INVALID
            - PENDING_VALIDATION
          description: Overall validation status of the order.
        createdAt:
          type: string
          format: date-time
          description: When the order was created.
        updatedAt:
          type: string
          format: date-time
          description: When the order was last updated.
        expiresAt:
          type: string
          format: date-time
          description: When the order will expire if not submitted.
    Pagination:
      type: object
      additionalProperties: false
      properties:
        nextCursor:
          type: string
          nullable: true
          description: Opaque token for fetching the next page. Null when no more results.
    EmbeddedCustomer:
      type: object
      description: >-
        Customer information embedded in responses. Sensitive details require
        separate API calls with appropriate authorization.
      required:
        - customerId
        - name
      properties:
        customerId:
          type: string
          description: The unique identifier for the customer.
        name:
          type: string
          description: The customer's display name.
    Error:
      type: object
      required:
        - message
        - code
      properties:
        message:
          type: string
          description: A human-readable message providing more details about the error.
        code:
          type: string
          description: A machine-readable code for the error.
        details:
          type: array
          description: Additional details about the error.
          items:
            type: object
            required:
              - message
              - code
            properties:
              message:
                type: string
                description: >-
                  A human-readable message providing more details about the
                  error.
              code:
                type: string
                description: A machine-readable code for the specific detail.
              property:
                type: string
                description: The property or field related to the error.
              suggestion:
                $ref: '#/components/schemas/Any'
                description: >
                  A suggested value for the particular property.


                  For example, this may be set when validating an address with
                  an alias, suggesting the expected value by the operator.
        hint:
          type: string
          description: A hint to help resolve the error.
    Any:
      oneOf:
        - type: string
        - type: number
        - type: boolean
        - type: object
          additionalProperties: true
        - type: array
  responses:
    BadRequest:
      description: The request was malformed or invalid.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: Authentication is required to access this resource.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Forbidden:
      description: Access to this resource is forbidden.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    TooManyRequests:
      description: Too many requests have been sent in a given amount of time.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    InternalServerError:
      description: An unexpected error occurred on the server.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: X-Api-Key
      description: >
        An API key that grants access to the Connect API. You can create and
        manage API keys in the portal.
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >
        Bearer authentication with JWT tokens is used to authenticate users.


        Do note that a valid API keys is also required to access the Connect API
        to prove that requests are made by a trusted party.


        Requests with a JWT token is scoped to the permissions of the user the
        token belongs to, regardless of the API key used.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.