Inventory History
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:/sandbox-api.shipbob.com/2026-01 - Endpoint:
/inventory/history:query
Production
- Base url:
https://api.shipbob.com/2026-01 - Endpoint:
/inventory/history:query
Response
Response schema
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. Note that for some event categories (such as InventoryAdjusted spot-check events), the decrement may be null when the event only results in an increase.
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 example, 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.
additional_reference
The additional_reference array contains supplementary key-value pairs that provide context specific to the event category. For InventoryAdjusted events originating from a spot check, this array will include the bin number, spot check reason ID, and spot check reason name.
InventoryAdjusted example response
For InventoryAdjusted spot check events, the primary_reference.type will be "SpotCheck" and the primary_reference.value will contain the spot check ID. The additional_reference array will contain the following keys:
The following spot check reason IDs and their corresponding names are supported:
Supported Event Categories
The following event categories can be sent via the POST request:
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://api.shipbob.com/2026-01/inventory/history:query?cursor=23456
This will return any records after (not including) the cursor value.

