Logistics & Supply Chain · Integration
Shipwire
Add Shipwire to your product for your customers, and give your AI agents governed access to it.
Shipwire is a fulfilment network rather than a single warehouse: a customer's stock sits in several locations and an order is served from whichever one can reach the buyer, which is also how cross border shipping is handled. An embedded Shipwire integration submits orders, quotes a rate before anything is committed, reads stock by product across the network, creates and follows receivings when a customer sends inventory in, and reads returns. Because inventory is distributed, the useful question is not how much stock exists but where it is, so warehouse level reads matter more here than a single total. Ownership of the business has changed hands more than once, so the connector follows the Shipwire platform itself rather than any one parent. fastn keeps the per-customer credentials and maintains the API surface.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Shipwire account so your product submits orders into the network holding their stock.
Quote a rate for a destination before your product promises a delivery cost to a buyer.
Read stock per product and per warehouse so your product can say which options are genuinely available near someone.
Create a receiving when a customer sends inventory in, then follow it until it is available to sell.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent says which warehouse an order will ship from and what that implies for the arrival date.
An agent reports stock sitting in the wrong region for where the demand actually is.
An agent submits or holds an order within governed permissions, with the action attributed to the account that authorised it.
Example prompt
Where is this customer's stock held across the network, and which warehouse would serve an order to Berlin?
Set up Shipwire in 4 steps
- 01Enable the Shipwire connector in your fastn dashboard.
- 02Have each customer authorise their own Shipwire account so orders and stock reads stay inside it.
- 03Map the order, product and warehouse fields your product uses, then enable rate quoting and the reads you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Shipwire integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Shipwire integration without building it. Your customers connect their own Shipwire account inside your product and work their shipments, tracking events and orders there, with no per-customer code on your side.
- Handle the part that actually costs time: tracking data arrives from many carriers in inconsistent formats and at unpredictable times. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Shipwire update is not your on-call problem.
- One integration serves your product and your agents. The same governed Shipwire connection powers in-product features and gives AI agents scoped, audited access, so you keep physical movement and stock visible inside your product without wiring it twice.
Used by these teams
Compare with
Often used alongside
Tools the same teams tend to run next to Shipwire, across other categories.
Shipwire integration FAQ
How do I add a Shipwire integration to my product?
Enable the Shipwire connector in your fastn dashboard, then let each customer authenticate their own Shipwire account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Shipwire client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Shipwire account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Shipwire account and only ever sees their own shipments, tracking events and orders. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Shipwire integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent says which warehouse an order will ship from and what that implies for the arrival date.
Who maintains the Shipwire integration?
fastn does. When Shipwire changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I track shipments from Shipwire inside my product?
Yes. Shipment and tracking events are read per customer and can trigger your workflows, so status changes surface in your product instead of your users checking a carrier site.
What does my product get back from Shipwire as things move?
Whatever Shipwire actually holds. Where it moves goods, that is shipment and tracking events, read per customer and delivered as they land. Where it holds stock, levels can be read on demand or kept in step through events, so your product is not deciding on a stale count. Where it carries orders and documents between trading partners, it is the acknowledgement, ship notice or status change that says what moved.
What can I build with the Shipwire integration?
A common starting point: let each customer connect their own Shipwire account so your product submits orders into the network holding their stock. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Shipwire integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Shipwire does not change your per-connector cost. You can start free with 3 connected accounts.
Add Shipwire to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.