Integrating ShipBob (Inventory)
Auth: OAuth 2.0 · Partner program: not required · Setup time: about 20 minutes · Last verified: 2026-05-23
ShipBob is a 3PL fulfillment network with a developer-facing REST API. The adapter wraps ShipBob’s Inventory endpoints and surfaces SKUs, inventory levels per fulfillment center, lots, and bins into the canonical inventory schema.
Auth model
Section titled “Auth model”- OAuth 2.0 Authorization Code grant (multi-merchant apps). Authorize at
https://auth.shipbob.com/connect/authorize. Exchange via POST tohttps://auth.shipbob.com/connect/token. - Sandbox uses
https://authstage.shipbob.com/connect/authorize+/connect/token. - Access tokens last
3600seconds. Includeoffline_accessin the scope set to receive arefresh_token. - Single-merchant deploys may use a Personal Access Token (PAT) generated from the ShipBob dashboard instead.
Prerequisites
Section titled “Prerequisites”- A ShipBob merchant account at shipbob.com (or sandbox).
- Register an OAuth app under Integrations → OAuth Apps → Create App. Note the Client ID and Client Secret, and register the exact callback URL — ShipBob enforces strict redirect matching.
- The connecting merchant must have access to the channel(s) you intend to read from; ShipBob scopes most data per
shipbob_channel_id.
Configure in admin
Section titled “Configure in admin”- Open
/platformsin the admin UI, filter to Inventory, click ShipBob. - Fill Configure:
clientId— from your ShipBob OAuth app.clientSecret— from your ShipBob OAuth app.redirectUri—${PUBLIC_BASE_URL}/auth/inventory/shipbob-inventory/callback.environment—productionorsandbox.
- Enable the adapter.
Required scopes
Section titled “Required scopes”For the canonical inventory surface request:
inventory_read,inventory_writeproducts_read,products_writelocations_readchannels_readwebhooks_read,webhooks_writeoffline_access— required for refresh tokens.
(Drop the _write variants if the integration is read-only.)
Webhooks
Section titled “Webhooks”ShipBob delivers JSON webhooks for inventory + order events. Configure subscriptions via the Webhooks API or the dashboard. The adapter verifies the per-subscription HMAC-SHA256 signature in the X-ShipBob-Hmac-Sha256 header (base64) against the raw body.
Subscribe to inventory_quantity_changed, inventory_received, and product_updated for the inventory surface.
Quirks worth knowing
Section titled “Quirks worth knowing”shipbob_channel_idis required on every call. Inventory data is scoped per channel; the OAuth token alone is not enough — pass the channel header.- Sandbox is a separate host.
authstage.shipbob.comfor OAuth,sandbox-api.shipbob.comfor data — production tokens won’t authenticate against sandbox. - Refresh requires
offline_access. Omit it and you’ll be re-prompting users every hour. - PAT vs OAuth. Single-merchant integrations can skip OAuth entirely with a PAT generated in the dashboard.
References
Section titled “References”opensteward.dev ·Plans and free license ·Terms ·Privacy ·support@opensteward.dev
© 2026 Falco Consulting AB. Built from open-steward/opensteward@a3961d8. This site sets no cookies, runs no analytics and loads nothing from other sites, except platform logos from Brandfetch on the Platforms page.