ShipStation (v1 Legacy) integration
ShipStation (v1 Legacy) integration for AI agents.
ShipStation (v1 Legacy) integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves ShipStation (v1 Legacy) tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
What your agents can do
Real ShipStation (v1 Legacy) actions, managed and audited.
Your user connects ShipStation (v1 Legacy) once; your agent can then use the legacy ShipStation v1 API to manage orders, shipments, carriers, stores, warehouses, products, customers, users, fulfillments, and webhooks — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants ShipStation (v1 Legacy) access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Tools & triggers
Supported ShipStation (v1 Legacy) tools.
47 tools are generated from the published ShipStation (v1 Legacy) catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 47 tools. All published catalog entries are included in this page's server-rendered HTML.
- Add funds to carrier account
- Adds funds to a carrier account using the payment information on file. **IMPORTANT:** Requires approval from apisupport@shipstation.com before use.
- carriers
- Add tag to order
- Adds a tag to an order
- orders
- Assign user to order
- Assigns a user to an order. If ANY of the orders within the array are not found, no orders will have a user assigned to them.
- orders
- Create label for order
- Creates a shipping label for an existing order. The `labelData` field returned in the response is a base64 encoded PDF value. You can decode and save the output as a PDF file to retrieve a printable label. **IMPORTANT:** You must have at least one active Manual Store on your ShipStation account to create labels with this endpoint.
- orders
- Create shipping label
- Creates a shipping label. The `labelData` field returned in the response is a base64 encoded PDF value. You can decode and save the output as a PDF file to retrieve a printable label. **IMPORTANT:** You must have at least one active Manual Store on your ShipStation account to create labels with this endpoint.
- shipments
- Create or update multiple orders
- Create or update multiple orders in one request. If the `orderKey` is specified, ShipStation will attempt to locate the order with that key. If found, the existing order will be updated. If not found, a new order will be created. For split orders, the `orderKey` is always required when creating or updating orders, and the `orderId` is always required for updates. This call does not currently support partial updates; the entire resource must be provided in the body of the request. Only orders in an open status (`awaiting_payment`, `awaiting_shipment`, `pending_fulfillment`, `on_hold`) can be updated. Orders in `cancelled` or `shipped` status may not be updated.
- orders
- Create or update order
- Create a new order or update an existing order. If the `orderKey` is specified, ShipStation will attempt to locate the order with that key. If found, the existing order will be updated. If not found, a new order will be created with that `orderKey`. **Note:** This call does not currently support partial updates. The entire resource must be provided in the body of the request. Only orders in an open status (`awaiting_payment`, `awaiting_shipment`, `on_hold`) can be updated. Orders in `cancelled` and `shipped` states may not be updated.
- orders
- Create warehouse
- Adds a Ship From Location (formerly known as warehouse) to your account. **Note:** In the API, the endpoint is called warehouse, but the process actually affects Ship From Locations in the UI.
- warehouses
- Deactivate store
- Deactivates the specified store
- stores
- Delete order
- Removes order from ShipStation's UI. This is a "soft" delete action so the order will still exist in the database, but will be set to inactive.
- orders
- Delete warehouse
- Removes a warehouse from ShipStation's UI and sets it to Inactive status. This is a "soft" delete action. **Note:** In the API, the endpoint is called warehouse, but the process actually affects Ship From Locations in the UI.
- warehouses
- Get carrier by code
- Retrieves the shipping carrier account details for the specified carrierCode. Use this method to determine a carrier's account balance.
- carriers
- Get customer
- Retrieves a single customer by ID
- customers
- Get order
- Retrieves a single order by its ID
- orders
- Get product
- Retrieves a single product by its ID
- products
- Get shipping rates
- Retrieves shipping rates for the specified shipping details. Use this endpoint to compare rates across different carriers and services before creating a label.
- shipments
- Get store
- Retrieves information for a specific store by its ID
- stores
- Get store refresh status
- Retrieves the refresh status of a given store
- stores
- Get warehouse
- Returns a specific Ship From Location (formerly known as warehouse). **Note:** In the API, the endpoint is called warehouse, but the process actually affects Ship From Locations in the UI.
- warehouses
- Hold order until date
- Changes the status of the order to On Hold until the specified date, when the status will automatically change to Awaiting Shipment.
- orders
- List account tags
- List all tags defined for this account
- accounts
- List carriers
- List all shipping providers connected to this account
- carriers
- List customers
- Obtains a list of customers that match the specified criteria
- customers
- List fulfillments
- Obtains a list of fulfillments that match the specified criteria. **Note:** Orders that have been marked as shipped either through the UI or API will appear in the response as they are considered fulfillments.
- fulfillments
- List marketplaces
- Lists the marketplaces that can be integrated with ShipStation
- stores
- List orders
- Obtains a list of orders that match the specified criteria. All filters are optional. If no filters are provided, recent orders will be returned.
- orders
- List orders by tag
- Obtains a list of orders that have been tagged with the specified tagId
- orders
- List packages
- Retrieves a list of packages for the specified carrier
- carriers
- List products
- Obtains a list of products that match the specified criteria
- products
- List services
- Retrieves the list of available shipping services provided by the specified carrier
- carriers
- List shipments
- Obtains a list of shipments that match the specified criteria. **Note:** Only valid shipments with labels generated in ShipStation will be returned. Orders that have been marked as Shipped through the UI or API will not appear as they are considered external shipments.
- shipments
- List stores
- Retrieve the list of installed stores on the account
- stores
- List users
- Retrieves a list of users for the account
- users
- List warehouses
- Retrieves a list of your Ship From Locations (formerly known as warehouses). **Note:** In the API, the endpoint is called warehouse, but the process actually affects Ship From Locations in the UI.
- warehouses
- List webhooks
- Retrieves a list of registered webhooks for the account
- webhooks
- Mark order as shipped
- Marks an order as Shipped without creating a label in ShipStation
- orders
- Reactivate store
- Reactivates the specified store. **Note:** Stores are active by default.
- stores
- Refresh store
- Initiates a store refresh. If storeId is not specified, a store refresh will be initiated for all refreshable stores on that account.
- stores
- Remove tag from order
- Removes a tag from the specified order
- orders
- Restore order from hold
- Changes the status of the order from On Hold to Awaiting Shipment. This endpoint is used when a holdUntilDate is attached to an order.
- orders
- Subscribe to webhook
- Subscribes to a specific type of webhook. If a store_id is passed in, the webhooks will only be triggered for that specific store_id. **Note:** Webhooks can only be modified through the ShipStation UI under Account Settings.
- webhooks
- Unassign user from order
- Unassigns a user from an order. If ANY of the orders within the array are not found, no orders will have their users unassigned.
- orders
- Unsubscribe from webhook
- Unsubscribes from a certain webhook
- webhooks
- Update product
- Updates an existing product. This call does not currently support partial updates. The entire resource must be provided in the body of the request.
- products
- Update store
- Updates an existing store. This call does not currently support partial updates. The entire resource must be provided in the body of the request.
- stores
- Update warehouse
- Updates an existing Ship From Location (formerly known as warehouse). **Note:** In the API, the endpoint is called warehouse, but the process actually affects Ship From Locations in the UI.
- warehouses
- Void shipment label
- Voids the specified label by shipmentId
- shipments
FAQ
ShipStation (v1 Legacy) integration, answered
- How do AI agents use ShipStation (v1 Legacy) through Open Connector?
- Your user connects ShipStation (v1 Legacy) once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes ShipStation (v1 Legacy) tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a ShipStation (v1 Legacy) MCP server?
- Yes. Open Connector can serve ShipStation (v1 Legacy) as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call ShipStation (v1 Legacy) actions with credentials injected server-side.
- Where do ShipStation (v1 Legacy) credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents ShipStation (v1 Legacy) — keep the keys.
Open source, self-hostable, with ShipStation (v1 Legacy) credentials that never leave your infrastructure. Run it from source today.