Migrate an existing ShipStation V1 API integration to the ShipStation API V2
domain: docs.shipstation.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Recognize that ShipStation API V1 and V2 are separate systems: V1 API keys are not valid for V2, and V2 requires generating new, separate credentials.
Audit which V1 endpoints your integration depends on (order sync, label purchase, rate shopping) and check V2's Shipping and Inventory endpoint coverage, since V2 is an early-release API and does not yet mirror every V1 capability.
Plan to use V2-only capabilities not available in V1 — such as batch label creation, return labels, and manifest endpoints — when redesigning the integration.
Re-implement any plugin or app configuration that existed against V1; settings do not automatically carry over to V2 and must be reconfigured from scratch.
Confirm your ShipStation plan tier: V1 API access is now limited to Gold, Scale, or higher-tier plans, so accounts on lower tiers must move to V2 to retain programmatic access.
Known gotchas
Because V1 and V2 have different authentication and are different systems, this is effectively a parallel build-and-cutover rather than an in-place upgrade — plan for a transition period running both.
V2 being in early release means some V1-only functionality may still be missing; verify feature parity for your specific workflow before deprecating the V1 integration.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?