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

# List transactions

> Organisation-level accounting transactions (an allocation links a transaction to a project, so transactions are not nested under a project). Requires the `transactions:read` scope. The full provider payload and internal exclusion audit fields are never exposed.



## OpenAPI

````yaml /openapi.json get /transactions
openapi: 3.1.0
info:
  title: Ledgitify REST API
  version: 1.0.0
  description: >-
    Programmatic access to a single organisation's Ledgitify projects, reports,
    allocations, and transactions. The API key alone determines which
    organisation is accessed; there is no tenant parameter on any endpoint.
    Every endpoint is read-only (GET) except `POST /transactions`, which pushes
    transactions in and requires the `transactions:write` scope.
  contact:
    name: Ledgitify
    url: https://ledgitify.com
servers:
  - url: https://ledgitify.com/api/v1
    description: Production
security:
  - ApiKeyAuth: []
tags:
  - name: Projects
    description: Projects and their budget-vs-actual reports
  - name: Allocations
    description: Allocations recorded against a project's budget lines
  - name: Transactions
    description: Organisation-level accounting transactions
paths:
  /transactions:
    get:
      tags:
        - Transactions
      summary: List transactions
      description: >-
        Organisation-level accounting transactions (an allocation links a
        transaction to a project, so transactions are not nested under a
        project). Requires the `transactions:read` scope. The full provider
        payload and internal exclusion audit fields are never exposed.
      operationId: listTransactions
      parameters:
        - name: from
          in: query
          required: false
          description: Inclusive lower bound on the transaction date (ISO 8601).
          schema:
            type: string
            format: date
        - name: to
          in: query
          required: false
          description: Inclusive upper bound on the transaction date (ISO 8601).
          schema:
            type: string
            format: date
        - name: status
          in: query
          required: false
          description: Filter by review status.
          schema:
            $ref: '#/components/schemas/TransactionStatus'
        - name: type
          in: query
          required: false
          description: Filter by transaction type.
          schema:
            $ref: '#/components/schemas/TransactionType'
        - name: page
          in: query
          required: false
          description: 1-based page number.
          schema:
            type: integer
            minimum: 1
            default: 1
        - name: pageSize
          in: query
          required: false
          description: Rows per page.
          schema:
            type: integer
            minimum: 1
            maximum: 200
            default: 50
      responses:
        '200':
          description: A page of transactions.
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                  - page
                  - pageSize
                  - total
                  - hasMore
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/Transaction'
                  page:
                    type: integer
                  pageSize:
                    type: integer
                  total:
                    type: integer
                  hasMore:
                    type: boolean
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '429':
          $ref: '#/components/responses/RateLimited'
components:
  schemas:
    TransactionStatus:
      type: string
      enum:
        - unreviewed
        - excluded
        - partially_allocated
        - fully_allocated
        - needs_review
    TransactionType:
      type: string
      enum:
        - bank_transaction
        - bill
        - invoice
        - journal_line
    Transaction:
      type: object
      required:
        - id
        - provider
        - providerTransactionId
        - type
        - status
        - date
        - description
        - totalAmount
        - currency
        - trackingCategories
      properties:
        id:
          type: string
        provider:
          type: string
          enum:
            - xero
            - quickbooks
            - manual
            - api
        providerTransactionId:
          type: string
        type:
          $ref: '#/components/schemas/TransactionType'
        status:
          $ref: '#/components/schemas/TransactionStatus'
        date:
          type: string
          format: date-time
        description:
          type: string
        contact:
          type:
            - string
            - 'null'
        totalAmount:
          type: number
        currency:
          type: string
        accountCode:
          type:
            - string
            - 'null'
        trackingCategories:
          type: array
          items:
            type: string
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              enum:
                - unauthorized
                - forbidden
                - insufficient_scope
                - not_found
                - rate_limited
            message:
              type: string
  responses:
    Unauthorized:
      description: Missing, malformed, unknown, or revoked API key.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: unauthorized
              message: Invalid or revoked API key.
    Forbidden:
      description: >-
        The plan does not include API access, or the key lacks the required
        scope.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          examples:
            planGate:
              value:
                error:
                  code: forbidden
                  message: API access is not available on this plan.
            scope:
              value:
                error:
                  code: insufficient_scope
                  message: This key lacks the reports:read scope.
    RateLimited:
      description: Per-key rate limit exceeded (120 requests/minute).
      headers:
        Retry-After:
          description: Seconds until the limit resets.
          schema:
            type: integer
        X-RateLimit-Limit:
          description: The per-minute request limit.
          schema:
            type: integer
        X-RateLimit-Remaining:
          description: Requests remaining in the current window.
          schema:
            type: integer
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: rate_limited
              message: Rate limit exceeded.
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: lk_live_...
      description: >-
        API key as a Bearer token: `Authorization: Bearer lk_live_<48 hex>`.
        Create keys in Settings → API keys (Owner or Admin); the full key is
        shown once. API access is a Professional+ feature. Each key is granted
        one or more scopes — read (`projects:read`, `reports:read`,
        `allocations:read`, `transactions:read`) and the single write scope
        (`transactions:write`) — and is limited to 120 requests per minute.

````