What we do
Tools
Industries
Department
How we workLet's talk →
Home/ShipEngine
ShipEngine

ShipEngine API: It Quotes and Prints, Your Code Decides

ShipEngine, from Auctane, is shipping you call from code: rates across carriers, labels, address validation and tracking. ShipStation's V2 API is built on it, and the ShipEngine guides now live on ShipStation's developer site, so don't be thrown when a page says "ShipStation API". What ShipEngine doesn't do is choose. Which carrier wins, what happens when one is down and where a tracking update should land are all yours to write.

Where ShipEngine stops

It's an API, so somebody still has to wire labels, rates and tracking to the order system, accounting and support.

Stuck on ShipEngine? Let's solve it →

From a TEST_ key to a label that costs real money

  1. 1

    Take a sandbox key from the dashboard

    Keys come from the ShipEngine dashboard. Sandbox keys always start with TEST_ and are meant for development. Send the key in an API-Key header to https://api.shipengine.com (or api.eu.shipengine.com). A missing or wrong key returns 401.

    Watch for: the sandbox allows only 20 requests a minute, so a load test there tells you nothing about production.

  2. 2

    Validate the address, then quote

    Run the destination through address validation before rating, so a bad apartment number fails now rather than at the carrier. Then request rates for the shipment and keep the response, since the label call can reference the rate you chose.

  3. 3

    Purchase it from the chosen rate

    Create the label from the chosen rate or from full shipment details. Store the label ID and tracking number against your own order ID straight away, because they're what voids and tracking lookups need later.

  4. 4

    Swap in the production key

    Anything done on a production key can incur charges, so keep it out of test scripts and CI. The production default is 200 requests a minute; ShipEngine raises it on request through a support ticket.

    Watch for: a 429 carries a Retry-After header. Retry from one global queue so a backlog doesn't stampede back all at once.

  5. 5

    Register webhooks for what happens next

    Setup Webhooks Create Webhook

    In production, add webhooks under Setup, then Webhooks, or POST to the webhooks endpoint. Events include track, batch and rate, and you get one URL per event; a second one returns 409.

ShipEngine returns the data; these calls are still yours

The job What ShipEngine gives you What your code has to decide
Picking a carrier for each order Every rate from every carrier account you connected The rule: cheapest under a weight, fastest for a promised date, a preferred carrier for a region, and what to do when two tie.
A carrier that errors or quotes oddly high The error, or the strange rate Failover to a second carrier, a ceiling on what you'll pay, and who gets told when the backup is used.
Tracking updates A track webhook with the tracking number and its events Which order it belongs to, and whether it updates the order record, the support ticket, the customer email, or all three.
Trusting a webhook An RSA-SHA256 signature over the timestamp and raw body, with keys published at /jwks Verifying it before acting, and answering 2xx inside 10 seconds. After up to two more tries, roughly 30 minutes apart, the event is dropped.

An order that leaves with a label and nobody touched it

The integrations that stall are usually the ones built for the common order. A subscription box business might have its storefront create orders cleanly while fulfillment staff still copy addresses into a label tool and paste tracking numbers back, one order at a time, because the code never handled a second carrier or an oversize box.

n-frames finishes that flow on the ShipEngine API: an order anywhere in your stack calls ShipEngine, the carrier rule you agreed picks the rate, the label is bought and the shipment record updates itself. Track events reach the order system, the help desk and the customer at once rather than whichever one was wired first. If you're weighing a hosted dashboard instead, the ShipStation API page covers V1 and V2, and EasyPost and Shippo are the nearest alternatives as APIs.

Questions people ask

What is ShipEngine?

A shipping API from Auctane, the company behind ShipStation. It quotes rates across carriers, prints labels, validates addresses and tracks packages, and it's built to be called from your own software rather than run from a merchant dashboard.

Where do I find ShipEngine's API documentation?

The guides and reference have moved under ShipStation's developer site, at docs.shipstation.com, in the ShipEngine section; old shipengine.com/docs links redirect there. Read the auth, rate-limit and webhook guides before writing code, since that's where most production surprises come from.

Is ShipEngine the same as ShipStation?

Related, not the same. Both are Auctane products. ShipStation is the dashboard merchants ship from, and its V2 API runs on ShipEngine. ShipEngine on its own is the developer API for putting shipping inside your own app or platform.

What is the ShipEngine API rate limit?

200 requests a minute by default in production, and 20 a minute in the sandbox. Over the limit you get a 429 with a Retry-After header. Higher production limits are available by asking ShipEngine's support.

Does ShipEngine send a webhook when a label is created?

Not in its event list. The webhook events cover tracking (track), completed batches, rate updates, carrier connections and a couple of beta order events. Record the label in your own system from the response to the label call.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.