Does ShipStation have an API?
Yes, two of them. V1 is the older REST API, built around orders, with Basic auth. V2 is newer, built around shipments, labels and inventory, and authenticates with an API-Key header. Both are separate from the dashboard your team ships from.
How do I get a ShipStation API key?
In ShipStation, go to Settings, then API Settings, choose V1 or V2 and generate the key. V1 gives you a key and a secret. A V2 key is shown only once, so save it straight away. The same page tells you if your plan doesn't include API access.
Does the ShipStation API support webhooks?
Yes. V1 webhooks fire on events such as a new order or a shipment going out, and send a resource_url you call to fetch the details. V2 has its own webhooks, so check its event list before porting a V1 listener across.
Can I manage ShipStation's automation rules through the API?
Not directly. Rules are set up in the dashboard. The API reads and writes the orders and shipments those rules act on, so integrations usually set the fields a rule matches on instead.
Does ShipStation support EDI?
Not natively. If a trading partner requires EDI documents such as an 850 purchase order or an 856 ship notice, you need an EDI provider or a custom translation layer that talks to ShipStation through its API. n-frames builds that layer.
What is the ShipStation API rate limit?
On V1 it's 40 requests a minute for each key and secret pair, and going over returns a 429. V2's rate-limit guide gives its own default and sends a Retry-After header with each 429. Either way, retry from one shared queue, not from each request.
Should a new ShipStation integration use V1 or V2?
Use V2 for labels, batches, returns, rates and inventory. Use V1 when you need to create and list orders, since V2 doesn't fully expose them yet. If you need both, run them side by side with a key for each. ShipStation's own docs recommend V2 wherever possible and maintain V1 for existing integrations, so write a V1 order sync so it can move to V2 later.