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

# List eligible invoices

> Lists invoices available for cash application, with their eligibility.



## OpenAPI

````yaml openapi-public-preview.json GET /v1/cash-applications/invoices
openapi: 3.1.0
info:
  title: Entendre API
  version: 1.0.0
  description: Programmatic access to crypto-native accounting and treasury operations.
servers:
  - url: https://api.entendre.finance
    description: Production API.
security:
  - ApiKey: []
tags:
  - name: Organization
    description: Read your organization profile and find members for agent assignments.
  - name: Transactions
    description: Find transactions, inspect their details and create manual records.
  - name: Sources
    description: >-
      Manage wallets, exchange accounts, bank accounts and other transaction
      sources.
  - name: Assets
    description: Inspect asset acquisitions, remaining quantities and cost basis.
  - name: Journals
    description: >-
      Create and post journal entries, correct eligible entries and sync posted
      journals to a connected general ledger.
  - name: Documents
    description: >-
      Upload documents, check processing status and link supporting evidence to
      transactions.
  - name: Legal Entities
    description: Manage the legal entities used in your accounting records.
  - name: Ledger Accounts
    description: Manage your chart of accounts and find accounts for journal entries.
  - name: Tags
    description: Create and manage tags to classify your records.
  - name: Accruals
    description: >-
      Create and post accruals, inspect their status and reverse eligible
      entries.
  - name: Cash Application
    description: Match deposits to invoices and manage the resulting cash applications.
  - name: Classification
    description: >-
      Classify transactions in a batch, post eligible entries and inspect the
      results.
  - name: Revaluation
    description: Run asset revaluations for an accounting period and check their results.
  - name: Accounting Periods
    description: Check whether a period is ready to close, then close or reopen it.
  - name: Income Statement
    description: View revenue, expenses and net income for a reporting period.
  - name: Balance Sheet
    description: View assets, liabilities and equity as of a reporting date.
  - name: Trial Balance
    description: Review ledger account balances and debit and credit totals.
  - name: Closing Positions
    description: View asset positions at the end of a reporting period.
  - name: Treasury Balances
    description: Review treasury balances by asset and source.
  - name: Realized Gains & Losses
    description: Review realized gains and losses from asset dispositions.
  - name: Asset Tax Lots
    description: Inspect asset tax lots, remaining quantities and cost basis.
  - name: Schedule of Dispositions
    description: >-
      Review asset dispositions and their proceeds, cost basis and gains or
      losses.
  - name: Financial Insights
    description: Review financial insights for your selected reporting context.
  - name: Agents
    description: Create agents, schedule their work and inspect their runs.
  - name: Memory
    description: Read, search and maintain the memory files your agents use.
  - name: Connections
    description: Connect providers, manage authorization and disconnect.
  - name: GL Mapping
    description: >-
      Map ledger accounts and legal entities to your ERP. Import legal entities,
      tags and chart of accounts.
  - name: Request
    description: Request information, documents or connections from a client.
  - name: Client
    description: Manage your firm’s client relationships.
  - name: Team
    description: Invite team members and manage their access to your firm.
  - name: Settings
    description: Read and update your firm settings.
paths:
  /v1/cash-applications/invoices:
    get:
      tags:
        - Cash Application
      summary: List eligible invoices
      description: >-
        List Stripe invoices available for cash application, with their
        eligibility. Legal entity and currency filters are not supported. The
        response’s `legal_entity_id` is always `null`.
      operationId: list_eligible_invoices
      parameters:
        - name: limit
          in: query
          required: false
          description: Page size (1-100). Defaults to 100 when omitted.
          schema:
            type: integer
            minimum: 1
            maximum: 100
        - name: cursor
          in: query
          required: false
          description: >-
            The `next_cursor` value from the previous page. Keep the other
            filters unchanged.
          schema:
            type: string
        - name: customer_name
          in: query
          required: false
          description: >-
            Customer name, matched as a substring without case sensitivity.
            `stripe_customer_id` takes precedence. A name that matches several
            customers returns an empty page.
          schema:
            type: string
            minLength: 1
            maxLength: 256
        - name: stripe_customer_id
          in: query
          required: false
          description: Stripe customer id.
          schema:
            type: string
            minLength: 1
            maxLength: 256
        - name: status
          in: query
          required: false
          description: >-
            Comma-separated invoice statuses: `open` (the default), `paid`,
            `draft`, `void` or `uncollectible`. An unknown value matches
            nothing.
          schema:
            type: string
            minLength: 1
            maxLength: 64
        - name: amount
          in: query
          description: >-
            Match invoices by amount due. Use tolerance to widen the amount
            range.
          schema:
            type: string
        - name: tolerance
          in: query
          description: >-
            Requires amount. Non-negative range around the requested amount;
            defaults to 5.
          schema:
            type: string
        - name: date_from
          in: query
          required: false
          description: >-
            Inclusive lower bound on invoice date. A bare `YYYY-MM-DD` date or a
            full ISO 8601 timestamp.
          schema:
            type: string
        - name: date_to
          in: query
          required: false
          description: >-
            Inclusive upper bound on invoice date. A bare `YYYY-MM-DD` date is
            clamped to end-of-day UTC; a full ISO 8601 timestamp is the exact
            instant (not clamped).
          schema:
            type: string
      responses:
        '200':
          description: A page of invoices eligible for cash application.
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                  - has_more
                  - next_cursor
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/V1CashApplicationInvoice'
                    description: The records.
                  has_more:
                    type: boolean
                    description: Whether another page is available.
                  next_cursor:
                    type:
                      - string
                      - 'null'
                    description: Cursor for the next page, or `null` on the last page.
                  resolution:
                    type: object
                    description: Customers that match `customer_name`.
                    properties:
                      customer_name:
                        type:
                          - string
                          - 'null'
                        description: Customer name that you sent.
                      stripe_customer_id:
                        type:
                          - string
                          - 'null'
                        description: Stripe customer ID, when one customer matched.
                      message:
                        type:
                          - string
                          - 'null'
                        description: Explanation of the match.
                      candidates:
                        type: array
                        items:
                          type: object
                          additionalProperties: true
                        description: Customers that match the name.
              example:
                data:
                  - id: inv_507f1f77bcf86cd799439011
                    invoice_number: '1001'
                    customer_name: Acme Corp
                    customer_id: cus_acme
                    status: open
                    amount_due: '100.00'
                    total_amount: '100.00'
                    invoice_date: '2026-08-01T00:00:00.000Z'
                    due_date: '2026-08-31T00:00:00.000Z'
                    currency: USD
                    legal_entity_id: null
                    transaction_id: null
                    provider: stripe
                    eligible: true
                    ineligibility_reason: null
                has_more: false
                next_cursor: null
          headers:
            X-Request-Id:
              description: Support correlation ID.
              schema:
                type: string
        '400':
          description: >-
            The request is invalid. `error.fields` lists the fields to correct.
            Nothing was changed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: VALIDATION_ERROR
                  message: Invalid path, query or request body.
                  request_id: req_example
        '401':
          description: The API key is missing, invalid or expired.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: UNAUTHORIZED
                  message: Authentication is required.
                  request_id: req_example
        '403':
          description: >-
            The API key does not have the required scope or is not associated
            with a user, or the action needs a review in the dashboard.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: FORBIDDEN
                  message: Insufficient access to organization
                  request_id: req_example
        '404':
          description: The resource does not exist, or your organization cannot access it.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: RESOURCE_NOT_FOUND
                  message: Resource not found
                  request_id: req_example
        '429':
          description: >-
            Too many requests. If the response has a `Retry-After` header, wait
            that many seconds before you retry. Otherwise, read `error.message`.
          headers:
            Retry-After:
              description: Seconds to wait before retrying.
              schema:
                type: integer
                minimum: 1
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: RATE_LIMITED
                  message: Rate limit exceeded. Retry after 30s.
                  request_id: req_example
        '500':
          description: >-
            An unexpected error occurred. A write can still have taken effect;
            check the resource before you retry. Give the `request_id` to
            support.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: INTERNAL_ERROR
                  message: Internal server error
                  request_id: req_example
        '503':
          description: >-
            A service that this operation needs is unavailable. If the response
            has a `Retry-After` header, wait that many seconds. Check for
            earlier accepted work before you send the request again.
          headers:
            Retry-After:
              description: Seconds to wait before retrying.
              schema:
                type: integer
                minimum: 1
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error:
                  code: SERVICE_UNAVAILABLE
                  message: Service unavailable.
                  request_id: req_example
components:
  schemas:
    V1CashApplicationInvoice:
      type: object
      description: A Stripe invoice, with its cash-application eligibility.
      required:
        - id
        - invoice_number
        - customer_name
        - customer_id
        - amount_due
        - currency
        - legal_entity_id
        - transaction_id
        - provider
        - eligible
        - ineligibility_reason
      properties:
        id:
          type: string
          description: Invoice ID (`inv_…`).
          example: inv_507f1f77bcf86cd799439011
        invoice_number:
          type:
            - string
            - 'null'
          description: Provider invoice number.
        customer_name:
          type:
            - string
            - 'null'
          description: Customer name.
        customer_id:
          type:
            - string
            - 'null'
          description: Stripe customer id (provider reference).
        status:
          type:
            - string
            - 'null'
          description: >-
            Stripe invoice status: `draft`, `open`, `paid`, `uncollectible`, or
            `void`.
        amount_due:
          type: string
          description: >-
            Decimal string; parse with a decimal library, not binary floating
            point.
          pattern: ^-?[0-9]+(?:\.[0-9]+)?$
          example: '100.00'
        total_amount:
          type: string
          description: Invoice total (decimal string).
          pattern: ^-?[0-9]+(?:\.[0-9]+)?$
          example: '100.00'
        invoice_date:
          type:
            - string
            - 'null'
          format: date-time
          description: Invoice issue date (ISO 8601).
        due_date:
          type:
            - string
            - 'null'
          format: date-time
          description: Invoice due date (ISO 8601).
        currency:
          type: string
          example: USD
          description: Invoice currency.
        legal_entity_id:
          type:
            - string
            - 'null'
          description: 'Always `null`: invoices are not linked to a legal entity.'
        transaction_id:
          type:
            - string
            - 'null'
          description: Transaction ID (`txn_…`) of the linked deposit, when one exists.
        provider:
          type: string
          enum:
            - stripe
          description: Always `stripe`.
        eligible:
          type: boolean
          description: True only while the invoice is `open` with a positive `amount_due`.
        ineligibility_reason:
          type:
            - string
            - 'null'
          enum:
            - paid
            - void
            - draft
            - uncollectible
            - zero_amount_due
            - null
          description: Set when `eligible` is false.
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
            - request_id
          properties:
            code:
              type: string
              description: Machine-readable error code.
            message:
              type: string
              description: Technical description for developers.
            fields:
              type: object
              additionalProperties:
                type: string
              description: >-
                Present only on VALIDATION_ERROR. Maps failing field paths to
                reason strings.
            details:
              type: object
              additionalProperties: true
              description: >-
                Optional redacted diagnostic details. Request validation uses
                fields or field_errors.
            suggested_action:
              type: string
              description: A suggested next step.
            documentation_url:
              type: string
              format: uri
              description: Link to documentation about this error.
            request_id:
              type: string
              description: Unique request ID for support escalation.
          description: Error details.
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: X-API-Key
      description: >-
        Your organization API key. Some operations also need a key that is
        associated with a user; their pages say so.

````