> 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/itemmovements.md).

# Item Movements

Item Movements Query

Returns a paginated list of ItemMovement objects, 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` | `ItemMovementOrder`      | Ordering options for movements returned from the connection            |
| `where`   | `ItemMovementWhereInput` | Filtering options for movements returned from the connection           |

## Return Type

`ItemMovementConnection!` - A connection to a list of ItemMovement objects with pagination information.

## Usage Example

```graphql
query {
  # Get all pending movements for a specific item
  itemMovements(
    where: {
      itemID: "item-123",
      executedAt_NULL: true
    },
    orderBy: { direction: ASC, field: CREATED_AT }
  ) {
    edges {
      node {
        id
        quantity
        fromRepositoryID
        toRepositoryID
        fromRepository {
          id
          name
        }
        toRepository {
          id
          name
        }
        item {
          sku
          data
        }
        blockedBy
        createdAt
      }
      cursor
    }
    totalCount
  }
}
```

```graphql
query {
  # Get blocked movements that need attention
  itemMovements(
    where: {
      blockedBy_NOT_NULL: true,
      executedAt_NULL: true
    },
    first: 20
  ) {
    edges {
      node {
        id
        quantity
        blockedBy
        item {
          id
          sku
        }
        fromRepository {
          id
          name
        }
        toRepository {
          id
          name
        }
        createdAt
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}
```

## Common Filters

* `executedAt_NULL: true` - Find pending movements
* `executedAt_NOT_NULL: true` - Find executed movements
* `blockedBy_NOT_NULL: true` - Find blocked movements
* `collectionID: "..."` - Find movements in a specific collection
* `fromRepositoryID` / `toRepositoryID` - Filter by source/destination
* `itemID` - Filter by specific item

## Notes

* Movements are created in pending state and executed later
* Use `executeInventoryItemMovement` mutation to execute a movement
* Blocked movements indicate issues like insufficient stock
* Virtual repositories bypass stock validation


---

# 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/itemmovements.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.