shipstation

Query and troubleshoot ShipStation API V2 and V1 endpoints from PowerShell.

2|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill shipstation-mbadali25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipstation
Source: https://github.com/mbadali25/useful-claude-add-ons/tree/main/skills/shipstation
Command: npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill shipstation-mbadali25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? ShipStation exposes three different APIs with different base URLs, auth schemes, and resource coverage, and picking the wrong one causes confusing 401/403/404 errors. This Skill guides correct API selection and provides a ready-made PowerShell client that handles auth, pagination, and rate-limit backoff. ## Core Features & Use Cases - API version routing: Explains that V2 covers shipments, labels, rates, carriers, warehouses, inventory, and fulfillments, while orders, customers, and stores exist only in legacy V1. - Ready-to-use query script: The included ss.ps1 script resolves credentials from environment variables or registry scopes, honours Retry-After headers on 429 responses, and follows pagination automatically. - Complete endpoint reference: endpoints.md lists all 142 V2 operations with methods, paths, and query parameters, plus instructions to verify against the live OpenAPI spec. - Use Case: Ask how many orders are awaiting shipment, and the Skill correctly routes to the V1 /orders endpoint with camelCase filters instead of inventing a nonexistent /v2/orders path. ## Quick Start Use the shipstation skill to list all shipments with status shipped from the last 30 days using ss.ps1 with pagination.

Frequently Asked Questions about shipstation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query the ShipStation API from PowerShell?

Use the included ss.ps1 script with an endpoint path, for example .\ss.ps1 /v2/shipments -Query @{ shipment_status='shipped' } -All. It reads your key from the SHIPSTATION_API_KEY environment variable, handles the API-Key header, retries on 429, and follows pagination.

ShipStation API V2 vs V1: which should I use?

Use V2 (api.shipstation.com, API-Key header) for shipments, labels, rates, carriers, warehouses, inventory, and fulfillments. Use V1 (ssapi.shipstation.com, Basic auth) only for orders, customers, and stores, since V2 has no orders endpoint.

Why does ShipStation return 404 for /v2/orders?

There is no /v2/orders, /v2/stores, or /v2/customers path in the V2 API. Query orders through the V1 /orders endpoint instead, or approximate with V2 /v2/shipments using sales_order_id or store_id filters.

What auth header does the ShipStation V2 API use?

V2 uses a custom API-Key header containing your key, not Bearer tokens or Basic auth. V1 is different: it requires Basic auth with a base64-encoded key:secret pair, and a V2 key will not authenticate V1.

Why does the ShipStation API return 429 and how do I handle it?

ShipStation allows roughly 200 requests per minute and returns 429 with a Retry-After header when exceeded. The ss.ps1 script honours Retry-After automatically; otherwise prefer bulk endpoints and narrow filters before paginating.

What does a 403 error mean on the ShipStation API?

A 403 usually means the endpoint is gated by your ShipStation account plan or the key lacks scope, not that the key is invalid. A 401, by contrast, indicates a wrong or missing credential.