# List inventory transactions

Returns inventory transactions across all sales channels belonging to the authenticated merchant.

See the Pagination section in the API overview above for details on how pagination works.

Endpoint: GET /inventory/transactions
Version: 2.0.0
Security: BearerAuth

## Query parameters:

  - `limit` (integer)
    Number of items to return per page (for pagination)

  - `created_at[gt]` (string)
    Filter results created after this date (ISO 8601 format)

  - `created_at[lt]` (string)
    Filter results created before this date (ISO 8601 format)

  - `created_at[gte]` (string)
    Filter results created on or after this date (ISO 8601 format)

  - `created_at[lte]` (string)
    Filter results created on or before this date (ISO 8601 format)

  - `sku_id[in]` (array)
    Filter results by one or more SKU IDs

  - `trigger_action[in]` (array)
    Filter results by one or more inventory transaction trigger actions.
Common actions include: storage_box_add_manually, storage_box_reduce_manually, order_reserved, order_shipped, return_restocked, etc.

## Response 200 fields (application/json):

  - `data` (array)

  - `data.id` (integer, required)
    Unique identifier of the inventory transaction.

  - `data.action` (string,null)
    The type of action that triggered this transaction.
Common values include: storage_box_add_manually, storage_box_reduce_manually,
order_reserved, order_shipped, return_restocked, inventory_adjustment, etc.

  - `data.sku_id` (integer, required)
    ID of the SKU associated with this transaction.

  - `data.inventory_batch_id` (integer,null)
    ID of the inventory batch involved in the transaction, if applicable.

  - `data.source_category` (string,null)
    The inventory category from which stock was moved (e.g., "available", "reserved", "damaged").

  - `data.destination_category` (string,null)
    The inventory category to which stock was moved (e.g., "available", "reserved", "damaged").

  - `data.source_inventory_change` (integer, required)
    The quantity change in the source category (typically negative when stock is moved out).

  - `data.destination_inventory_change` (integer, required)
    The quantity change in the destination category (typically positive when stock is moved in).

  - `data.created_at` (string, required)
    Timestamp when the transaction was recorded.

  - `data.sku` (object,null)
    Summary of the SKU involved in the transaction.

  - `data.sku.id` (integer)
    Unique identifier of the SKU.

  - `data.sku.merchant_sku` (string,null)
    The merchant's internal SKU code.

  - `data.sku.name` (string,null)
    Display name of the SKU.

  - `data.inventory_batch` (object,null)
    Summary of the inventory batch involved in the transaction, if applicable.

  - `data.inventory_batch.id` (integer)
    Unique identifier of the inventory batch.

  - `data.inventory_batch.name` (string,null)
    Name or identifier of the batch (e.g., lot number, expiry date).

  - `pagination` (object)

  - `pagination.first_page_url` (string)
    URL to fetch the first page of results

  - `pagination.limit` (integer)
    Number of items returned per page

  - `pagination.next_page_url` (string,null)
    URL to fetch the next page of results. If null, there are no more results.

## Response 400 fields (application/json):

  - `errors` (any, required)
    Error information. Can be:
- Object with field names as keys and error arrays as values (for validation errors)
- Array of error objects with message, code, and optional metadata
- Array of strings (for simple error messages)

  - `success` (boolean)
    Indicates if the request was successful

  - `title` (string)
    A brief, human-readable message about the error

  - `status` (integer)
    HTTP status code

## Response 401 fields (application/json):

  - `errors` (any, required)
    Error information. Can be:
- Object with field names as keys and error arrays as values (for validation errors)
- Array of error objects with message, code, and optional metadata
- Array of strings (for simple error messages)

  - `success` (boolean)
    Indicates if the request was successful

  - `title` (string)
    A brief, human-readable message about the error

  - `status` (integer)
    HTTP status code

## Response 403 fields (application/json):

  - `errors` (any, required)
    Error information. Can be:
- Object with field names as keys and error arrays as values (for validation errors)
- Array of error objects with message, code, and optional metadata
- Array of strings (for simple error messages)

  - `success` (boolean)
    Indicates if the request was successful

  - `title` (string)
    A brief, human-readable message about the error

  - `status` (integer)
    HTTP status code

## Response 429 fields (application/json):

  - `errors` (any, required)
    Error information. Can be:
- Object with field names as keys and error arrays as values (for validation errors)
- Array of error objects with message, code, and optional metadata
- Array of strings (for simple error messages)

  - `success` (boolean)
    Indicates if the request was successful

  - `title` (string)
    A brief, human-readable message about the error

  - `status` (integer)
    HTTP status code