Transactions
Transactions Query
Returns a paginated list of Transaction objects representing stock changes, with optional filtering and ordering.
Arguments
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.
Usage Example
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
}
}Common Filters
itemID- Filter by specific itemrepositoryID- Filter by specific repositorytype- Filter by transaction typemovementID_NULL: true- Find manual adjustmentsquantity_GT: 0- Find incoming transactionsquantity_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
Last updated
Was this helpful?
