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

# List invoices

> The invoices Venly has issued to your company, most recent first.

**Requires scope:** `view:billing` — see [Required scopes](/getting-started/authentication#required-scopes-finance-api).

Reads your invoices live from our billing system — Finance stores none. Only issued (`SENT`) invoices are visible. To read them, open the billing portal at `billingUrl` on [your company profile](/api-reference/Finance-API/company/get-your-company-profile) — the per-invoice `sequenceUrl` is an internal reference, not a page you can open. The PDF is available through [Download an invoice PDF](/api-reference/Finance-API/billing/download-an-invoice-pdf).

<Note>This endpoint uses **cursor pagination**, not `page`/`size`. Send `nextPageCursor` / `previousPageCursor` back exactly as received. Until Venly has linked your company to a billing customer it answers `422 billing-not-configured`.</Note>

See [Billing](/guides/finance/billing).


## OpenAPI

````yaml api-reference/Finance-API-Specs.yaml GET /billing/invoices
openapi: 3.1.0
info:
  title: Venly Finance API
  description: >
    REST API for the Venly Finance platform:

    - Party management (Individuals & Organisations)

    - Identity verification — hosted KYC/KYB links and Sumsub share-token
    forwarding

    - Account management with party association

    - Wallet balances & token allowances on supported chains

    - Virtual bank accounts for global pay-in (EUR SEPA, USD ACH/WIRE/RTP/SWIFT)

    - Fiat-to-crypto payment sessions (pay-in)

    - Bank pay-outs — beneficiary allow-listing, routes, and PULL/PUSH pay-outs

    - Account-to-account fiat & crypto transfers

    - EIP-2612 permits and allowances

    - Webhook registration for asynchronous event delivery


    ## Authentication


    All endpoints use OAuth2 client credentials. Obtain a token first, then
    include it in every request:


    **Step 1 — Get a token:**

    ```bash

    curl -X POST
    https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
    \
      -H "Content-Type: application/x-www-form-urlencoded" \
      -d "grant_type=client_credentials&client_id={CLIENT_ID}&client_secret={CLIENT_SECRET}"
    ```


    **Step 2 — Use the token:**

    ```

    Authorization: Bearer {access_token}

    ```


    Tokens expire after **5 minutes**. Implement refresh logic in your client.


    ## Selecting a tenant


    A token that grants more than one tenant must say which one each request is
    for, in the

    `x-tenant-id` header. With a single-tenant token, omit it. Any value you
    send must exactly match a

    tenant the token grants; a missing, malformed or foreign value is answered
    with a generic

    `403 forbidden` that reveals nothing about which tenants exist. Send the
    header at most once.


    ## Request correlation


    Every response — including `401` and `403` — carries an `X-Correlation-Id`
    header identifying the

    operation in our logs. Quote it in a support request. You may supply your
    own, as

    `X-Correlation-Id` or (as a fallback) `X-Request-Id`, matching
    `^[A-Za-z0-9_.:-]{1,64}$`. A value

    outside that shape is replaced with a generated one rather than rejected.
  version: 1.10.0
  contact:
    name: Venly Support
    email: support@venly.io
    url: https://docs.venlyfinance.com
  license:
    name: Proprietary
  x-logo:
    url: https://venlyfinance.com/logo.png
  x-security-contact: security@venly.io
servers:
  - url: https://api.venlyfinance.com/v1
    description: Production
  - url: https://api-staging.venlyfinance.com/v1
    description: Staging
security:
  - OAuth2: []
tags:
  - name: Parties
    description: Party management (Individuals & Organisations)
  - name: Accounts
    description: Account management, party-role associations
  - name: Wallets
    description: Blockchain wallet balances
  - name: Virtual Bank Accounts
    description: Virtual bank account payment references for global payments
  - name: Fiat-to-crypto Payment Sessions
    description: >-
      Hosted fiat-to-crypto pay-in sessions. **Coming soon** — not yet enabled;
      use a virtual bank account to receive fiat today.
  - name: Payout Bank Accounts
    description: Allow-listing beneficiary bank accounts as pay-out destinations
  - name: Payout Routes
    description: >-
      Account-scoped routes pairing a beneficiary bank account with a crypto
      deposit asset
  - name: Payouts
    description: Crypto-to-fiat pay-outs over a registered route
  - name: Transfers
    description: Fiat and crypto transfer operations between accounts
  - name: Permits
    description: EIP-712 permit signature management for token approvals
  - name: Supported Assets
    description: >-
      Discover which chains and assets your tenant can settle in, and whether an
      account can use them yet.
  - name: Allowances
    description: Token allowance management for wallets
  - name: Webhooks
    description: Webhook registration, delivery testing and delivery history
  - name: Pay-Ins
    description: >-
      The pay-in ledger — every fiat credit that settled (or failed to settle)
      into an account wallet
  - name: Billing
    description: The invoices Venly has issued to your company
  - name: API Credentials
    description: Self-service management of your company's OAuth client credentials
  - name: Company
    description: Your own company profile
paths:
  /billing/invoices:
    parameters:
      - $ref: '#/components/parameters/TenantId'
    get:
      tags:
        - Billing
      summary: List invoices
      description: >
        **Requires scope:** `view:billing`


        The invoices Venly has issued to your company, most recent first, read
        live from our billing

        system. Finance stores no invoices: this is a company-scoped proxy, and
        every invoice carries a

        deep link to the full document in the billing dashboard.


        Only issued (`SENT`) invoices are visible; drafts, unsent and voided
        invoices are excluded.

        Download the PDF through `GET /billing/invoices/{invoiceId}/download`.


        Which billing customer your company maps to is provisioned by Venly.
        Until it is, this endpoint

        answers `422 billing-not-configured`; once it is, a company with no
        invoices yet gets an empty

        page.


        **Cursor pagination.** Like the webhook delivery listing — and unlike
        every other list endpoint —

        this one is *not* paginated with `page`/`size` and does not return the
        `pagination`/`sort`

        envelope. Send `nextPageCursor` or `previousPageCursor` back exactly as
        received to move between

        pages.
      operationId: listInvoices
      parameters:
        - name: size
          in: query
          required: false
          description: Page size
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 100
        - name: nextPageCursor
          in: query
          required: false
          description: >
            Opaque cursor from a previous page, to move forward. Send it back
            exactly as received — it is

            not a stable identifier and must not be constructed by hand. Supply
            either this or

            `previousPageCursor`, never both.
          schema:
            type: string
            maxLength: 1024
        - name: previousPageCursor
          in: query
          required: false
          description: Opaque cursor from a previous page, to move back
          schema:
            type: string
            maxLength: 1024
      responses:
        '200':
          description: >-
            One page of invoices; `content` is empty when the company has no
            invoices yet
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InvoicePageResponse'
              example:
                success: true
                result:
                  content:
                    - id: 7f68c0d4-4d55-4bd8-9b0e-1cfb0255c554
                      invoiceNumber: INV-042
                      status: SENT
                      paymentStatus: PAID
                      currency: EUR
                      netTotal: '1250.00'
                      totalTax: '262.50'
                      grossTotal: '1512.50'
                      issueDate: '2026-09-01'
                      dueDate: '2026-09-15'
                      billingPeriodStart: '2026-08-01'
                      billingPeriodEnd: '2026-08-31'
                      sequenceUrl: >-
                        https://billing.example.com/invoices/7f68c0d4-4d55-4bd8-9b0e-1cfb0255c554
                      createdAt: '2026-09-01T06:00:00Z'
                  pagination:
                    size: 100
                    hasNextPage: false
                    hasPreviousPage: false
        '400':
          description: >
            Invalid paging — a `size` outside 1..100, both cursors supplied at
            once, or a cursor the

            billing system no longer recognises (`invalid-cursor` — stale or
            malformed; restart from the

            first page).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          description: >-
            Forbidden — the token lacks `view:billing`, a dedicated scope
            because what Venly charges your company is commercially sensitive.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '422':
          description: >-
            `billing-not-configured` — your company is not linked to a billing
            customer yet.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: '`billing-provider-error` — the billing system rejected the request.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '503':
          description: >-
            `billing-provider-unavailable` — the billing system could not be
            reached. Retry.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  parameters:
    TenantId:
      name: x-tenant-id
      in: header
      required: false
      description: >
        Which tenant the request is scoped to, among those your token grants.
        Omit it when the token

        grants exactly one tenant; it is **required** when the token grants more
        than one. A supplied

        value must exactly match a tenant the token grants.


        Absent when required, blank, malformed, or naming a tenant the token
        does not grant — each gets

        the same generic `403 forbidden`, which reveals neither whether a tenant
        exists nor which ones

        you may use. Send the header once: a repeated header is rejected the
        same way.
      schema:
        type: string
        format: uuid
        example: 3fa85f64-5717-4562-b3fc-2c963f66afa6
  schemas:
    InvoicePageResponse:
      allOf:
        - $ref: '#/components/schemas/BaseResponse'
        - type: object
          properties:
            result:
              $ref: '#/components/schemas/InvoicePage'
    ErrorResponse:
      type: object
      description: Error response wrapper
      properties:
        success:
          type: boolean
          description: Always false for error responses
          example: false
        errors:
          type: array
          description: List of errors that occurred
          items:
            $ref: '#/components/schemas/ErrorBody'
        result:
          type: object
          nullable: true
          description: Null or omitted when success is false
    BaseResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Indicates whether the request was successful
    InvoicePage:
      type: object
      description: >
        One cursor-delimited page of invoices. Deliberately **not** the
        `result`/`pagination`/`sort`

        envelope the other list endpoints return — the billing system paginates
        by opaque cursor, so

        `page`/`size` cannot be honoured.
      required:
        - content
        - pagination
      properties:
        content:
          type: array
          items:
            $ref: '#/components/schemas/Invoice'
        pagination:
          $ref: '#/components/schemas/InvoicePagination'
    ErrorBody:
      type: object
      description: Individual error details
      properties:
        code:
          type: string
          description: Machine-readable error code
          example: invalid-request
        message:
          type: string
          description: Human-readable error message
          example: The request contains invalid parameters.
    Invoice:
      type: object
      description: >
        One invoice Venly issued to your company, read live from our billing
        system. Finance stores no

        invoices. `sequenceUrl` is Venly's internal reference to the invoice and
        is not a page you can

        open; read your invoices in the billing portal at `billingUrl` on

        [Get your company
        profile](/api-reference/Finance-API/company/get-your-company-profile),
        or

        download one with [Download an invoice
        PDF](/api-reference/Finance-API/billing/download-an-invoice-pdf).
      required:
        - id
        - status
        - sequenceUrl
      properties:
        id:
          type: string
          format: uuid
          description: Invoice id in the billing system
        invoiceNumber:
          type: string
          description: Human-readable invoice number
          example: INV-042
        status:
          type: string
          description: Issuance status. Only `SENT` invoices are exposed by this API.
          example: SENT
        paymentStatus:
          type: string
          description: >
            Collection status, passed through verbatim — a separate vocabulary
            from `status`. Values at

            the time of writing: `UNPAID`, `PARTIALLY_PAID`, `PAID`,
            `UNCOLLECTIBLE`.
          example: PAID
        currency:
          type: string
          description: ISO 4217 currency code
          example: EUR
        netTotal:
          type: string
          description: Net amount as a decimal string
          example: '1250.00'
        totalTax:
          type: string
          description: Tax amount as a decimal string
          example: '262.50'
        grossTotal:
          type: string
          description: Gross amount as a decimal string
          example: '1512.50'
        issueDate:
          type: string
          format: date
        dueDate:
          type: string
          format: date
        billingPeriodStart:
          type: string
          format: date
          description: >-
            Start of the billing period covered; absent for invoices not tied to
            a billing schedule
        billingPeriodEnd:
          type: string
          format: date
          description: >-
            End (inclusive) of the billing period covered; absent with
            `billingPeriodStart`
        sequenceUrl:
          type: string
          format: uri
          description: >
            Venly's internal reference to this invoice in the billing system.
            Not a page you can open —

            use `billingUrl` on your company profile, or download the PDF.
        createdAt:
          type: string
          format: date-time
          description: When the invoice was created in the billing system
    InvoicePagination:
      type: object
      description: >
        Cursor pagination state — the same shape as the webhook delivery
        listing. There is no page

        number or total count; cursors must be sent back exactly as received.
      required:
        - size
        - hasNextPage
        - hasPreviousPage
      properties:
        size:
          type: integer
          description: Number of entries requested for this page
        hasNextPage:
          type: boolean
        hasPreviousPage:
          type: boolean
        nextPageCursor:
          type: string
          description: >-
            Send back as `nextPageCursor` to fetch the following page; absent on
            the last page
        previousPageCursor:
          type: string
          description: >-
            Send back as `previousPageCursor` to fetch the preceding page;
            absent on the first page
  responses:
    Unauthorized:
      description: Authentication required or failed (401)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: unauthenticated
                message: Please authenticate to perform this action.
  securitySchemes:
    OAuth2:
      type: oauth2
      description: >
        OAuth2 client credentials flow. Token endpoints:

        - Staging:
        https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token

        - Production:
        https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
      flows:
        clientCredentials:
          tokenUrl: >-
            https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
          scopes: {}

````

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