The whole platform, open to your code.
The typical 3PL API stops at pushing orders and pulling tracking. Jetpack opens the surfaces the platform itself runs on, and lets you build any tools you need to compete.
I have built, scaled, and exited an ops-heavy B2B e-commerce service provider, and now find myself on the client side building my own consumer brand. So I recognize and have special appreciation for outstanding logistics partners like Jetpack.
Matt, Nora, and team are true pros, and a rare breed. They know logistics, and are willing to tackle even the hairiest of startup challenges with poise. They feel like a direct extension of our small team, and their flexibility and partnership have been invaluable as we’ve scaled.
Six surfaces, from inbound to returned.
Push orders in from any system, read stock as it moves, register inbound, process returns, follow every shipment in flight. If the platform is doing it, your code can see it.
Orders
Push orders from your store, ERP, or custom checkout, then read back status and line items as each one moves through fulfillment.
Inventory
Read live stock across all 60+ warehouses, broken out as on hand, fulfillable, sellable, and committed. Lot items carry batch and expiration data.
Products
Create and manage the catalog Jetpack fulfills against, including bundles where one sellable SKU resolves to multiple inventory items.
Receiving
Open warehouse receiving orders in code to send inventory into the network, with box labels generated for the warehouse to process.
Returns
Create returns with restock, dispose, or quarantine handling per item, each one linked back to its original outbound shipment.
Tracking
Every fulfilled order produces shipment records with carrier tracking numbers, ship method, and live status through delivery.
Your systems hear about it the moment it happens.
Subscribe once and events land on your endpoint as they happen: an order ships, tracking updates, a delivery lands, a return completes, an inbound box gets scanned. No polling. No stale nightly syncs. Pair the delivery-exception event with Delivery IQ and your team hears about problems before customers do.
Every payload is signed so your endpoint can verify the source, and failed deliveries retry automatically.
- Order shipped
- Tracking updated
- Shipment delivered
- Delivery exception
- Return created
- Return completed
- Inbound box scanned
- Charge created
A sample of the events you can subscribe to. Each one fires as a signed payload to your endpoint the moment it happens.
An integration you write once and stop worrying about.
The API is versioned, so what you build today keeps working as the platform grows. A sandbox lets you wire up the whole flow before launch. Tokens carry exactly the access they need.
Sandbox first
Stand up a sandbox account and run the full integration, orders through receiving, before a single unit of inventory arrives.
Versioned releases
Releases carry dated versions, so the platform keeps shipping new capability without breaking the integration you already run.
Scoped access
Use a personal access token for your own stack or OAuth 2.0 for multi-user apps. Every token is scoped to the access it needs, served over HTTPS.
Ask during your demo and we’ll hand your team the full reference docs, OpenAPI spec included.
What is a 3PL API?
What it is
A 3PL API is the programmatic doorway into your fulfillment provider. Instead of a person reading a dashboard and re-keying numbers into your systems, your systems ask directly: push an order in, read stock levels back, check where a shipment is right now. Anything fulfillment knows becomes data your stack can act on, the moment it needs it.
Why it matters
Without an API, fulfillment data is trapped behind someone else’s login. Finance reconciles invoices by hand. Support tabs between systems to answer one tracking question. Your ERP runs a day behind the warehouse, and every workaround becomes another spreadsheet someone has to babysit. Past a thousand orders a month, manual glue stops holding. The data exists; it just is not flowing to the systems that need it.
How Jetpack does it
Jetpack’s API is versioned REST with scoped tokens, webhooks that push events to your endpoint in real time, and a sandbox for building before your inventory arrives. Most brands start with native integrations and reach for the API when their stack outgrows off-the-shelf.
Or skip the code entirely.
Shopify, Amazon, BigCommerce, NetSuite, and 50+ other platforms connect natively, syncing products and orders on their own. Most brands never write a line of code. The API is for everything past that: custom storefronts, ERPs, internal tools, finance systems.
The rest of the platform
- Technology StackThe whole platform, end to end.
- Jetpack ProEvery cost and shipment in one dashboard.
- Jetpack WMSThe warehouse platform behind your fulfillment.
- Jetpack CareA named team on Slack, not a ticket queue.
- MultiHub IQInventory placed closest to your buyers.
- Carrier IQThe optimal carrier for every package.
- Delivery IQStuck shipments flagged before customers notice.
- IntegrationsConnect the stack you already run.
Frequently asked.
Jetpack natively integrates with 50+ ecommerce platforms and apps: storefronts like Shopify, BigCommerce, WooCommerce, Wix, and Squarespace; marketplaces including Amazon, Walmart, eBay, and TikTok Shop; plus Klaviyo, Gorgias, Loop Returns, NetSuite, ShipStation, AfterShip, and EDI via SPS Commerce. Our integrated OMS, IMS, RMS, and WMS sync inventory, orders, and returns in real time across every channel and warehouse. Carrier IQ auto-selects the best carrier and service level for each package across ground, 2-day, and overnight.
Yes, fully automated. Lot-tracked products are stored separately by batch, and the system ships nearest-expiration inventory first via FIFO, so customers always get the freshest product without manual oversight. Set minimum shelf life days per SKU; units below that threshold are auto-excluded from fulfillment, so no expired product reaches a customer. Full recall readiness: trace exactly which orders received a specific batch and from which fulfillment center. Returns on lot-tracked products route to quarantine or disposal rather than restock, protecting active inventory.
An API (application programming interface) is how two software systems talk to each other automatically. In fulfillment, it means your store, your ERP, or your own custom tools can send orders to Jetpack and pull back live inventory counts, order statuses, and tracking numbers, with no spreadsheets and no manual re-entry. If your developer asks whether Jetpack has an API, the answer is yes: an open, documented one covering orders, inventory, products, receiving, returns, and tracking.
Almost everything the platform does. Push orders in from any system, read live inventory across the 60+ warehouse network, create and manage products and bundles, open inbound receiving orders, process returns, and follow every shipment's tracking and status. Webhooks push events to your systems in real time, and a sandbox lets you test the whole flow before launch. See the Technology Stack for how the API fits the wider platform.
Yes. Subscribe an endpoint and Jetpack pushes events as they happen: an order ships, tracking updates, a shipment delivers or hits an exception, a return is created or completed, inbound boxes arrive and get stowed. Payloads are signed so you can verify the source, and failed deliveries retry automatically. No polling loops, no stale data. Pair it with Delivery IQ and your team hears about problems before customers do.
Yes. A sandbox environment lets you build and test the entire integration, orders, products, inventory, and receiving included, before a single unit of real inventory arrives. Wire it up, simulate the flows, then switch to production once it behaves. Most teams build their integration in parallel with onboarding, so the connection is live by the time stock hits the warehouse.
Documentation is available upon request, including a full endpoint reference and an OpenAPI specification that drops into standard tooling. Ask during your demo, or through your Jetpack team if you are already a client, and we will set your developers up. If you would rather not write code at all, most platforms connect through native integrations instead.
No. Shopify, Amazon, BigCommerce, and 50+ other platforms connect through native integrations, with products and orders syncing automatically. The API exists for brands whose stack goes further: a custom storefront, an ERP that needs live fulfillment data, internal tools, finance systems reconciling invoices. If that is you, your developers get the same surfaces the platform runs on.
Two options. A personal access token covers single-brand custom integrations: quick to issue, simple to use. OAuth 2.0 covers multi-user applications, with granular permissions and expiring tokens. Every request authenticates with a bearer token over HTTPS, and access is scoped so an integration gets exactly what it needs and nothing more. Tokens are issued and managed from the dashboard.
See the platform in action.
Book a guided demo. We’ll walk you through the platform live, answer your integration questions, and set your developers up with the full API documentation.