What we do
Tools
Industries
Department
How we workLet's talk →
Home/ShipBob/ShipBob API for Wholesale and Second Channels
ShipBob

The ShipBob API, for Everything the Shopify App Doesn't Carry

Your Shopify or WooCommerce store already talks to ShipBob through the native app: orders go in, stock comes back, tracking lands on the order. Then a wholesale portal shows up, or finance wants an invoice the day a box leaves, and nothing in the app covers it. That's the job for the ShipBob API, and it takes a token, a channel ID and a version number to get started.

ShipBob API setup

Your own integration: a personal access token, generated on the dashboard while signed in as the root user. Since it never expires, keep it somewhere safer than a config file.

Integrations API Tokens Generate New Token

An app other merchants will install: OAuth 2.0, required for the ShipBob App Store. Access tokens last an hour and refresh tokens 30 days.

Calls: https://api.shipbob.com/2026-07/..., with sandbox at sandbox-api.shipbob.com. GET /channel gives you the ID to send as shipbob_channel_id on most POSTs.

Limit: 150 requests a minute on a sliding window, per user and application. A 429 comes with x-retry-after telling you how many seconds to wait.

ShipBob endpoints and webhooks, matched to the job

The job What to call or subscribe to Watch for
Orders from a wholesale portal or marketplace with no ShipBob app POST /order with your channel ID, after an estimate if you want the shipping cost first. Use a channel whose scopes include write access, and keep the portal's own order number on the ShipBob order so a retry can find it.
Live stock for a channel the native apps miss GET /inventory-level, by location and by lot where you need it. Send each channel one combined available figure, not the per-location numbers, or two channels end up promising the same units.
An invoice or customer email the day an order ships The order.shipped webhook, then order.shipment.tracking.updated for later carrier scans. order.shipped waits until every label on a split order is printed. Use order.delivered for the whole order arriving.
Shortages and holds someone has to act on The order.shipment.exception and order.shipment.on_hold webhooks. Route each one to the person who can fix it, an address problem to support and an out-of-stock to purchasing.
Inbound stock and fulfillment costs Receiving orders (WROs) with the wro.* webhooks, and the invoices and transactions endpoints with billing.* events. Match ShipBob's charges to orders in your books before month-end, not after.

A home goods brand selling wholesale from its ShipBob stock

Home goods brand · Shopify store and a wholesale portal, one ShipBob inventory

Before

The brand added a wholesale portal next to its Shopify store, both selling from the same ShipBob stock.

Each channel kept its own idea of what was left, so one could oversell against the other.

After

n-frames built the sync on ShipBob's API that keeps both channels on one accurate count.

The store and the portal now show the same number for every product.

ShipBob API habits that cost orders or quota

Posting orders without the channel header

How you'll know: POST /order keeps coming back rejected, even though the token works fine for reads.

Fix: Fetch the channels once, pick the one with write scopes for this integration, and send it as shipbob_channel_id on every POST.

Polling orders to spot shipments

How you'll know: The sync burns through 150 calls a minute asking about orders that haven't changed.

Fix: Subscribe to the webhook topics you need and keep polling for a slow nightly cross-check only.

Trusting webhooks you haven't verified

How you'll know: Anyone who finds your URL could post a fake shipped event.

Fix: Check the webhook-signature header against your secret before acting, and answer with a 2xx quickly. ShipBob retries with exponential backoff when it doesn't get one.

Building against a deprecated version

How you'll know: Code copied from an older example uses v1.0 or v2.0 paths and topic names like order_shipped.

Fix: Use the dated versions, 2026-07 being the default now, and the dotted topic names that go with them.

ShipBob API and app questions

Does ShipBob have a Shopify app?

Yes. The native Shopify integration brings orders into ShipBob, sends stock levels back to the store and adds tracking to each order once it ships. A single store with standard fulfillment doesn't need the API at all.

Does ShipBob integrate with WooCommerce?

Yes, natively, covering the same loop as Shopify: order import, inventory updates and tracking. The API comes in when a second channel, a portal or a back-office system needs that data too.

Where do I log in to manage my ShipBob account?

At web.shipbob.com, the merchant dashboard for orders, inventory, receiving and billing. The sandbox has its own dashboard at webstage.shipbob.dev, and API tokens for each are generated from its dashboard.

What can I actually do with ShipBob's API?

Create, estimate and cancel orders; hold, release or re-address shipments; read inventory by location and lot; manage receiving orders and returns; pull invoices and transactions; and subscribe to webhooks for shipping, receiving, returns and billing events. n-frames uses it to feed channels and accounting systems the native apps don't reach.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.