> ## Documentation Index > Fetch the complete documentation index at: https://docs.telnesstech.com/llms.txt > Use this file to discover all available pages before exploring further. # List payment intents > Retrieve a paginated list of payment intents with optional filtering by status, customer, or date range. ## OpenAPI ````yaml /api-reference/bundled_openapi.json get /payment-intents 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: /payment-intents: get: tags: - Payment Intents summary: List payment intents description: >- Retrieve a paginated list of payment intents with optional filtering by status, customer, or date range. operationId: listPaymentIntents parameters: - $ref: '#/components/parameters/Limit' - $ref: '#/components/parameters/Cursor' - name: customerId in: query schema: type: array items: type: string description: Filter payment intents by customer IDs example: - e7f8a9b0-c1d2-3456-7890-567890123456 - f8a9b0c1-d2e3-4567-8901-678901234567 - name: status in: query schema: type: array items: $ref: '#/components/schemas/PaymentIntentStatus' description: Filter payment intents by status responses: '200': description: Payment intents retrieved successfully content: application/json: schema: type: object required: - items - pagination additionalProperties: false properties: items: type: array items: $ref: '#/components/schemas/PaymentIntentListItem' pagination: $ref: '#/components/schemas/Pagination' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '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: PaymentIntentStatus: type: string description: Current stage of a payment intent as it is collected over card rails. enum: - PENDING - REQUIRES_ACTION - PROCESSING - SUCCEEDED - REQUIRES_PAYMENT_METHOD - CANCELLED example: SUCCEEDED PaymentIntentListItem: type: object description: >- A payment intent without its nested attempts, refunds, and line items, optimized for list views. required: - paymentIntentId - customerId - status - amount - currency - createdAt - updatedAt additionalProperties: false properties: paymentIntentId: type: string description: The unique identifier for this payment intent. example: 64870b5c-fb61-4c9a-955a-e148e0826c20 customerId: type: string description: The customer this payment intent collects from. example: a1b2c3d4-e5f6-4a5b-8c9d-0e1f2a3b4c5d status: $ref: '#/components/schemas/PaymentIntentStatus' amount: type: number format: decimal description: The total amount to collect. example: 29 currency: type: string description: The currency of the amount. example: USD description: type: string description: A human-readable description of what is being collected. example: Mobile subscription renewal dueAt: type: string format: date-time description: When the amount is due. example: '2024-01-15T10:00:00Z' createdAt: type: string format: date-time description: When the payment intent was created. example: '2024-01-15T10:00:00Z' updatedAt: type: string format: date-time description: When the payment intent was last updated. example: '2024-01-15T10:00:00Z' Pagination: type: object additionalProperties: false properties: nextCursor: type: string nullable: true description: Opaque token for fetching the next page. Null when no more results. 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' 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. ````