Logistics & Supply Chain · Integration
ShipStation
Add ShipStation to your product for your customers, and give your AI agents governed access to it.
ShipStation is where a merchant who ships their own parcels turns an order into a label. It pulls orders in from the sales channels a customer sells on, rate shops across the carrier accounts they hold, buys or prints the label, and hands back the tracking number the buyer eventually sees. An embedded ShipStation integration reads and updates those orders, requests rates, creates shipments and labels, reads carriers, services and package types, and reacts to shipment events. The part you cannot hard-code is the carrier list: rates and services depend entirely on which carrier accounts that particular customer has connected, so your product has to ask rather than assume. fastn keeps each account's key and secret per tenant and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own ShipStation account so orders your product creates appear in the queue their warehouse staff already work.
Ask for rates across the carriers that customer genuinely holds accounts with, then buy the label they choose.
Write the tracking number and carrier back onto your own order record as soon as the label exists.
React to a shipment or delivery event so your product tells the buyer instead of sending them to a carrier site.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the cheapest service that still meets a promised delivery date for one shipment.
An agent explains where a parcel is by reading its tracking events, scoped to that customer's account.
An agent buys a label for an approved order within governed permissions, with the purchase logged.
Example prompt
What would it cost to get this order there by Thursday, and which carrier on the account can actually do it?
Set up ShipStation in 4 steps
- 01Enable the ShipStation connector in your fastn dashboard.
- 02Have each customer authorise their own ShipStation account so labels are bought against their carrier agreements.
- 03Map the order, shipment and rate fields your product uses, then enable the events you want to react to.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the ShipStation integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a ShipStation integration without building it. Your customers connect their own ShipStation 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 ShipStation update is not your on-call problem.
- One integration serves your product and your agents. The same governed ShipStation 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
Works well with
Often used alongside
Tools the same teams tend to run next to ShipStation, across other categories.
ShipStation integration FAQ
How do I add a ShipStation integration to my product?
Enable the ShipStation connector in your fastn dashboard, then let each customer authenticate their own ShipStation account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ShipStation client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ShipStation account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ShipStation 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 ShipStation 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 finds the cheapest service that still meets a promised delivery date for one shipment.
Who maintains the ShipStation integration?
fastn does. When ShipStation 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 ShipStation 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 ShipStation as things move?
Whatever ShipStation 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 ShipStation integration?
A common starting point: let each customer connect their own ShipStation account so orders your product creates appear in the queue their warehouse staff already work. 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 ShipStation integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ShipStation does not change your per-connector cost. You can start free with 3 connected accounts.
Add ShipStation to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.