> ## Documentation Index > Fetch the complete documentation index at: https://docs.ornn.com/llms.txt > Use this file to discover all available pages before exploring further. # List account transactions > Returns a page of your organization's account transactions, newest recorded first, with only your own postings. Events recorded for another party show only their type, time, and reservation. Pass next_cursor as cursor with the same filters to read older entries. An empty next_cursor marks the end. Omit cursor to restart from the newest entries. Pages are not a snapshot across requests. Requires an approved organization. ## OpenAPI ````yaml openapi.yaml GET /v1/ledger/transactions openapi: 3.1.0 info: title: Ornn compute API version: 1.0.0 description: >- Customer HTTP API for Ornn GPU capacity. It covers reserved capacity and nodes, VM and Bare Metal access, Kubernetes and Slurm clusters, SSH keys, storage volumes and GitHub repositories, private networks, monitoring, buying and selling capacity (Reserve, Market, Spot, and Relist), and billing. API keys are scoped to one organization and act with their creator's access there; account, team, and API-key management stay in the console. Most operations require an approved organization. See https://docs.ornn.com/api-keys to create a key and https://docs.ornn.com/guides/kubernetes-api for an end-to-end Kubernetes integration. Examples use fictional IDs and credentials. The info.version field identifies the contract revision, not a shared API path version. contact: email: support@ornn.com servers: - url: https://api.ornn.com description: Production security: - OrnnApiKey: [] tags: - name: Authentication - name: Reservations - name: GPU nodes - name: Clusters - name: Workers - name: Virtual machines description: >- Choose a VM disk, launch VM access on a reservation, and read each VM's status, launch progress, and SSH connection details. - name: Bare Metal description: >- Launch Bare Metal access on a reservation, read a host's readiness and SSH connection details, and reboot or hard reset it. - name: SSH keys description: >- Register public keys for your organization, choose which keys a VM or Bare Metal reservation uses, and queue key delivery to machines. Slurm clusters take organization key IDs at launch. Kubernetes API access does not use SSH keys. - name: Reserve description: >- Browse reserved-capacity listings and their terms, and post, cancel, or accept offers. Reserve listings are visible to approved organizations. - name: Market description: >- Browse relisted capacity and buy windows at the asking price, paid up front. Open to every member of your organization. - name: Spot description: >- Hourly order books for VMs with 1, 2, 4, or 8 GPUs on one node: read books, trades, and quotes, place and cancel bids, and follow fills. - name: Relist description: >- Sell whole nodes from a reservation you hold at your asking price, and manage those listings. - name: Storage description: >- Managed volumes, their files, and GitHub repository pulls. Volumes belong to the API key's creator in the key's organization. - name: Networks description: >- Organization private networks and the WireGuard configs you use to reach private machines and clusters. - name: Monitoring description: >- Machine telemetry and console logs for capacity your organization holds. Reads are limited to your reservation window. - name: Billing description: >- Invoices, billing summary, usage cost, Ornn credits, and account statements. Saving a card and paying invoices stay in the console. externalDocs: description: REST integration walkthrough url: >- https://docs.ornn.com/guides/kubernetes-access#provision-and-manage-through-rest paths: /v1/ledger/transactions: get: tags: - Billing summary: List account transactions description: >- Returns a page of your organization's account transactions, newest recorded first, with only your own postings. Events recorded for another party show only their type, time, and reservation. Pass next_cursor as cursor with the same filters to read older entries. An empty next_cursor marks the end. Omit cursor to restart from the newest entries. Pages are not a snapshot across requests. Requires an approved organization. operationId: platformListAccountTransactions parameters: - name: limit in: query required: false description: Maximum transactions per page. schema: type: integer minimum: 1 maximum: 500 default: 500 - name: cursor in: query required: false description: >- Opaque next_cursor from the previous page. Keep the same reservation filter. schema: type: string minLength: 1 maxLength: 128 - name: reservation_id in: query required: false description: Only transactions for this reservation. schema: type: string format: uuid responses: '200': description: Transactions. content: application/json: schema: $ref: '#/components/schemas/PlatformAccountTransactions' example: next_cursor: '' transactions: - ledger_transaction_id: eeeeeeee-eeee-4eee-8eee-eeeeeeeeeeee event: event_type: credit_applied source_id: example-source organization_id: 22222222-2222-4222-8222-222222222222 invoice_id: null payment_intent_id: '' reservation_id: 11111111-1111-4111-8111-111111111111 occurred_at: '2026-10-14T12:00:00Z' reverses_transaction_id: null recorded_at: '2026-10-14T12:00:01Z' postings: - account: organization_id: 22222222-2222-4222-8222-222222222222 account_role: ORNN_CREDIT currency: usd amount_cents: 2500 '400': description: >- An unexpected or malformed query parameter. Invalid limits and cursors include detail.code and detail.message. content: application/json: schema: anyOf: - $ref: '#/components/schemas/PlatformPlainError' - $ref: '#/components/schemas/Error' example: detail: code: invalid_cursor message: The cursor is invalid. Start again without a cursor. '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' default: $ref: '#/components/responses/Error' components: schemas: PlatformAccountTransactions: type: object properties: next_cursor: type: string description: >- Pass as cursor to read the next page. Empty when there are no more entries. transactions: type: array items: type: object properties: ledger_transaction_id: type: string format: uuid event: type: object description: >- What caused the transaction. Events recorded for another party contain only event_type, occurred_at, and reservation_id. properties: event_type: type: string description: >- Such as spot_hour_charged, credit_applied, or payment_recorded. source_id: type: string organization_id: type: string format: uuid invoice_id: type: - string - 'null' format: uuid payment_intent_id: type: string reservation_id: type: - string - 'null' format: uuid occurred_at: type: string format: date-time reverses_transaction_id: type: - string - 'null' format: uuid recorded_at: type: string format: date-time postings: type: array description: Your organization's postings only. items: type: object properties: account: $ref: '#/components/schemas/PlatformLedgerAccount' amount_cents: type: integer format: int64 PlatformPlainError: type: object description: Error body with a machine-readable string. Check the HTTP status first. required: - error properties: error: type: string Error: type: object properties: code: type: string detail: oneOf: - type: string - type: object required: - code - message properties: code: type: string message: type: string PlatformLedgerAccount: type: object properties: organization_id: type: - string - 'null' format: uuid account_role: type: string description: Such as ORNN_CREDIT. Handle roles you do not recognize. currency: type: string responses: Unauthorized: description: >- The credential is missing, invalid, revoked, or no longer belongs to a current organization member. Check the HTTP status before parsing the body. content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: >- The credential lacks access to this operation, or the organization requires approval. An API key does not bypass these checks. content: application/json: schema: $ref: '#/components/schemas/Error' Error: description: >- Unsuccessful request. Check HTTP status first. Errors may have detail.code/detail.message, a string detail and optional top-level code, or an empty/non-JSON body. 401: invalid credential; 403: access or approval required; 404: not visible or credentials not ready; 409: lifecycle conflict; 429: back off; 5xx: service failure. Inspect current state before retrying mutations. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: OrnnApiKey: type: http scheme: bearer bearerFormat: ornn_sk_... description: >- Create an organization API key in Account Settings > Developer. Do not send this key to the Kubernetes API server. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.