A ShipEngine alternative with unlimited API calls

What counts as a billable event on ShipEngine

ShipEngine prices access the way infrastructure vendors do: usage is the product, so usage is what gets metered. The decode that matters before you integrate is which of your calls the meter can see. A production label integration does far more than buy labels — it quotes at checkout, re-quotes when an address is corrected, validates destinations, polls or receives tracking, and retries everything that times out. Under a metered model, each of those behaviours is a line your plan has an opinion about, and the integration you write starts bending around the meter: you cache rates you would rather re-fetch, batch validations you would rather run inline, and think twice about a health check that costs money.

The second axis is carrier access. ShipEngine grows around carrier accounts you connect — your UPS number, your FedEx credentials — which is a genuine strength at contract-holding scale and a week of paperwork below it. Whether bringing your own carrier accounts beats a shared four-carrier panel is a whole argument of its own, and it is owned by the EasyPost comparison and the carrier-accounts page rather than re-run here.

ShipEngine plan structure — verified against ShipEngine's published pricing and docs on 2026-08-15. As of that date, ShipEngine's published plans meter usage with allowances and paid tiers, and define which operations count against them; the tier names, allowance sizes, and per-unit prices are deliberately not printed here because ShipEngine has repackaged its plans before and will again. Read the current definitions on ShipEngine's own pricing page before you model an integration's cost — including what its meter counts, which is the part that moves most. Re-check cadence: every 6 months, by the named review owner recorded with this page.

Unlimited calls, wallet-funded labels: how billing actually works here

The GoatLabels model deletes the meter instead of discounting it. Every API call is free, at any volume, on every plan: create shipments, list rates, validate addresses, read tracking, manage webhooks, and hammer your staging environment without a line item appearing anywhere. The one thing that moves money is a label purchase, and it moves money in the most literal way available — the all-in carrier rate you were quoted is debited from a prepaid wallet, the same wallet the dashboard uses, funded by card, Apple Pay, Google Pay, ACH, or crypto. Your shipping forecast becomes shipments times carrier rate, with no second term for the platform.

That structure changes how you write the integration. Quote-heavy patterns — cart estimates, background re-pricing, a re-quote on every address edit — stop being budget decisions. Retries are safe twice over: free at the request layer, and guarded by real idempotency keys at the purchase layer, so a timed-out buy that runs again returns the original label instead of buying a second one. The wider comparison of metered versus free API surfaces is worked through on the free shipping API page and EasyPost vs a free shipping API; this page's claim is narrower and checkable in an afternoon: nothing you can call at api.goatlabels.io has a price on it except the label.

Webhooks: signatures and the adjustment event

Webhooks are where label APIs quietly differ most, because they are the part you only evaluate after you have integrated. Every GoatLabels delivery is signed: an X-GoatLabels-Signature header carries a timestamp and an HMAC-SHA256 of the payload computed with your endpoint's secret, so your server verifies the sender instead of trusting it. Every delivery attempt — including each retry — writes its own row to a delivery log you can read back over the API, and any delivery can be replayed against your endpoint, which turns the debugging session every webhook consumer eventually has from guesswork into a diff.

The event most generic comparisons never list is shipment.adjustment.created. When a carrier re-rates a shipment after the fact — a re-weigh, a dimension correction — the adjustment is recorded as its own object, exposed at /v1/adjustments, and pushed to you with the wallet delta attached, so your reconciliation job hears about the correction the moment it exists instead of finding it in a month-end statement. One accuracy note belongs next to that: if an adjustment exceeds the wallet balance, the card on file is charged for the difference. How carriers detect, bill, and let you dispute these corrections is its own page; what this page owns is the fact that your code can subscribe to them.

POST /v1/webhooks
{ "url": "https://example.com/hooks/shipping",
  "events": ["shipment.adjustment.created", "shipment.delivered"] }

# each delivery arrives signed:
X-GoatLabels-Signature: t=1755216000,v1=hmac-sha256(secret, "t.body")

# and adjustments are readable as records, not statement lines:
GET /v1/adjustments
{ "object": "list", "data": [ { "shipment_id": "...",
  "reason": "carrier_reweigh", "wallet_delta": "-1.42" } ] }

Where ShipEngine's carrier breadth wins

The honest concession, in full: ShipEngine's carrier catalogue is far wider than four. If your routing guide includes regional parcel carriers, international postal operators, or LTL freight, GoatLabels cannot quote those lanes — USPS, UPS, FedEx, and DHL are the honest and complete list here. And if your company already holds negotiated contracts that beat any shared panel, an API built to drive your own accounts is the right architecture, and paying its meter is rational. Teams at that scale should stay, and this page will not pretend otherwise.

The team this page is for looks different: the big four cover their lanes, no negotiated contracts exist to bring, and the meter is pure friction — a cost on every quote their integration would prefer to make freely. For that team the evaluation is mechanical rather than rhetorical. Point a copy of your rating step at the API, log both responses for a week, and compare two things: the all-in numbers, and the absence of a usage line on this side of the ledger. The account, the key, and every call in that test are free, so the evaluation costs exactly the labels you choose to buy during it.