> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/queries/transactions.md).

# Transactions

Transactions Query

Returns a paginated list of Transaction objects representing stock changes, with optional filtering and ordering.

## Arguments

| Name      | Type                    | Description                                                            |
| --------- | ----------------------- | ---------------------------------------------------------------------- |
| `after`   | `Cursor`                | Returns the elements in the list that come after the specified cursor  |
| `first`   | `Int`                   | Returns the first *n* elements from the list                           |
| `before`  | `Cursor`                | Returns the elements in the list that come before the specified cursor |
| `last`    | `Int`                   | Returns the last *n* elements from the list                            |
| `orderBy` | `TransactionOrder`      | Ordering options for transactions returned from the connection         |
| `where`   | `TransactionWhereInput` | Filtering options for transactions returned from the connection        |

## Return Type

`TransactionConnection!` - A connection to a list of Transaction objects with pagination information.

## Notes

The `data` field contains custom transaction attributes as JSON. You can use the `Data`, `DataHasKey`, `DataIn`, and `DataContains` filters to query based on JSON content. For complex JSON field queries, see [Advanced JSON Field Queries](https://github.com/pyck-ai/docs/blob/main/graphql/advanced/json-field-queries.md).

## Usage Example

```graphql
query {
  # Get all transactions for a specific repository today
  transactions(
    where: {
      repositoryID: "warehouse-main",
      createdAt_GTE: "2024-01-15T00:00:00Z",
      createdAt_LTE: "2024-01-15T23:59:59Z"
    },
    orderBy: { direction: DESC, field: CREATED_AT }
  ) {
    edges {
      node {
        id
        quantity
        type
        createdAt
        item {
          sku
          data
        }
        repository {
          name
        }
        movement {
          id
          fromRepositoryID
          toRepositoryID
        }
      }
      cursor
    }
    totalCount
  }
}
```

```graphql
query {
  # Get stock adjustments (non-movement transactions)
  transactions(
    where: {
      movementID_NULL: true,
      type: ADJUSTMENT
    },
    first: 20
  ) {
    edges {
      node {
        id
        quantity
        type
        data
        createdAt
        createdBy
        item {
          sku
        }
        repository {
          name
        }
      }
    }
  }
}
```

## Common Filters

* `itemID` - Filter by specific item
* `repositoryID` - Filter by specific repository
* `type` - Filter by transaction type
* `movementID_NULL: true` - Find manual adjustments
* `quantity_GT: 0` - Find incoming transactions
* `quantity_LT: 0` - Find outgoing transactions

## Notes

* Transactions are immutable audit records
* Every executed movement creates two transactions (outgoing and incoming)
* Manual adjustments create single transactions
* Use for audit trails and historical analysis


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/queries/transactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.