This documentation provides an overview and API request examples for getting product inventory history events from ShipBob.

​
Overview

ShipBob’s Inventory History API can be used to fetch various inventory movements that occur within the ShipBob Network. An example of this is Warehouse Receiving Order (WRO) stow events as inventory is stowed at a fulfillment center. When stowing occurs, ShipBob’s On Hand quantity increases for that inventory item, and is considered ready to use for fulfillment. This API can be used to capture inventory events such as stow events, spot checks, restock events, and more.

​
Request

Method: POST Authorization: Bearer token, PAT generated from the ShipBob merchant dashboard. Sandbox
  • Base url: https://inventorymanagementapi-stage.shipbob.dev
  • Endpoint: /inventory/history:query
Production
  • Base url: https://gateway.shipbob.com
  • Endpoint: /inventory/history:query
{ 
  "inventory_ids": [2543121], // optional 
  // "merchant_user_id": null, // required (optional if using a PAT token) 
  "facility_id": 25, // required 
  "event_category": "ReceivingStow", 
  "start_date": "2025-06-18", // optional - last 90 days as default/max 
  "end_date": null // optional 
}

​
Response

Response schema 
{
  "inventory_id": 2543121,
  "event_category": "ReceivingStow",
  "event_datetime": "2025-06-18T18:06:22.4716033",
  "shipbob_order_id": null,
  "merchant_user_id": 226071,
  "primary_reference": {
    "type": "WroAndBox",
    "value": "115316 7"
  },
  "inventory_audit_event_id": 32204,
  "increment": {
    "facility_id": 25,
    "quantity_change": 1,
    "committed_quantity_change": 0,
    "lot_number": null,
    "expiration_date": null,
    "sku": "awe-jui",
    "location_id": 10010109,
    "yuki_id": "01JY23GXR7CSS4D25G5SC84VD1",
    "pack_description_id": "00000000000000000000000000",
    "operational_stage": null,
    "inventory_status": ""
  },
  "decrement": {
    "facility_id": 25,
    "quantity_change": -1,
    "committed_quantity_change": 0,
    "lot_number": null,
    "expiration_date": null,
    "sku": "awe-jui",
    "location_id": 10010277,
    "yuki_id": "01JXFHF4PQVVDW8AYVHXAVC7RM",
    "pack_description_id": "00000000000000000000000000",
    "operational_stage": null,
    "inventory_status": ""
  },
  "additional_reference": []
}
Each inventory event will include an increment and decrement object. The increment object is the event at the facility’s destination shelf, which updates the on-hand quantity for that item in ShipBob. The decrement object will decrease the specified quantity at the facility found within the object. In addition, the event includes the primary_reference property. Based on the Event Categories being queried, the type field will contain a definition for the corresponding value field. As an example, using the Event Category of “ReceivingStow” will return a type field of “WroAndBox”, and the value field will contain a combination of the WRO id and the box id. These two values will always be separated by a space. As another exmaple, using the Event Category of “OrderPicked” will return a type field of “OrderId” and a value field that will contain the ShipBob order id, in case it needs to be fetched in any subsequent steps within the integration workflow.

​
Supported Event Categories

The following event categories can be sent via the POST request:
EventCategoryDescription
OrderPickedThis will return any picking event that occurs during the outbound fulfillment process.
InventoryAdjustedEvents that occur due to an inventory adjustment, including found inventory during spot-checks and setting on-hand quantities.
InventoryFacilityUpdatedEvents that occur when updating the facility of inventory locations.
AttributeUpdatedEvents that occur when updating inventory attributes.
InventoryReceivedEvents related to receiving new inventory, including returns.
InventoryRestockedEvents related to restocking previously picked inventory.
ReceivingStowThis will return stow events that occur from WROs which updates On Hand quantities.
KittingStowEvents related to stowing inventory during the kitting process, including legacy kitting operations.

​
Pagination

The response includes the field inventory_audit_event_id which can be used as a cursor. Usage: Begin with an empty cursor. To fetch additional records, use the last inventory_audit_event_id as a query parameter in subsequent requests. Example: POST https://inventorymanagementapi-stage.shipbob.dev/inventory/history:query?cursor=23456 This will return any records after (not including) the cursor value.