Building on EasyPost?

EasyPost rates, trackers or webhooks acting up? We fix it.

EasyPost is a developer-facing shipping API, and the problems people call us for are almost always in the glue code: a Shipment created with the wrong parcel dimensions, a rate call that returns nothing because the carrier account is not fully onboarded, a Tracker that returns tracker.not_found because the tracking number was created outside EasyPost, or a webhook endpoint that times out under batch load. We clean up the integration against the carriers and the API doc at the same time.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

easypost-api.log

still broken

What it is

EasyPost at a glance

EasyPost is a shipping API founded in 2012 in Y Combinator's winter batch, aimed squarely at developers who need to add rating, label purchase, tracking and address verification to an application without writing a dedicated integration per carrier. It talks to USPS, UPS, FedEx, DHL, Canada Post, OnTrac, Deutsche Post, and a long tail of regional and international carriers behind one REST API.

The core objects are Address, Parcel, Shipment, Rate, Tracker, Pickup and Insurance. Rate shopping produces a list of Rate objects across connected carrier accounts; purchasing a Rate on a Shipment returns a PostageLabel. Smart Rate adds predicted delivery accuracy on top. Address verification, batch endpoints, carrier metadata and a Trackers API that works on third party tracking numbers (within limits) round out the surface. Most of the integration work we are called in on is parcel normalization, rate shopping that is quietly filtering carriers out, and webhooks that cannot keep up with Shipment and Tracker volumes.

Type
Multi-carrier shipping API
First released
2012 as a developer-facing shipping API
License
Proprietary API, usage-based pricing per label and per API call
Maintained by
EasyPost, Inc. (Lehi, Utah)
Typically used for
Rate shopping, label purchase, tracking, address verification inside custom commerce apps

The honest version

EasyPost pros and cons

No technology is all upside. This is where EasyPost earns its place and where it tends to cause trouble.

Where EasyPost is strong

  • Carrier coverage without a per-carrier projectUSPS, UPS, FedEx, DHL and dozens of regionals are reachable through the same API objects, so adding a new carrier is a configuration change rather than a sprint.
  • The API is genuinely well designedAddress, Parcel, Shipment, Rate and Tracker are consistent across carriers, and the error payloads are specific enough to reason about rather than guess.
  • Smart Rate predicts delivery accuracySmart Rate returns predicted delivery dates with accuracy percentages, which lets a checkout make an honest promise rather than a hopeful one.
  • Address verification saves moneyStrict and permissive address verification catches undeliverable addresses before a label is purchased, reducing returned packages and the fees that come with them.
  • Webhooks cover the important eventsTracker status updates, Shipment events and Batch events fire webhooks that let the application react to real world shipping events without polling the API.
  • Sandbox is actually usableThe test mode produces labels and events that look real, so integration work can be done against test carriers without touching a production USPS account.

Where EasyPost bites

  • Tracker on third-party tracking numbers is limitedTrackers created against tracking numbers that were not purchased through EasyPost can return tracker.not_found or incomplete event history, depending on the carrier.
  • Rate shopping silently filtersA carrier account in a verification state, a parcel.predefined_package the carrier does not recognize, or a destination outside service area will make a carrier drop out of the Rates list without an explicit error.
  • Carrier onboarding takes real timeUPS and FedEx accounts need credential verification and sometimes a physical address check that can sit in a needs_credentials state for days, and the API cannot speed that up.
  • Webhook retries are not forgivingEasyPost expects a fast 2xx response and will not retry forever, so an endpoint that is slow under load drops events rather than queueing them for later.
  • Pricing is easy to misestimatePer-label and per-API-call pricing combined with Smart Rate and verification fees can surprise a finance team that modelled on labels alone.
  • Carrier-specific features leak throughSCAN forms, pickup manifests, insurance maximums and label formats differ by carrier, and the common API abstracts most of it but not all.

Sound familiar?

Common EasyPost problems we fix

The EasyPost problems that bring people to us, and what you have once each one is fixed.

tracker.not_found

Tracker API cannot find a tracking number

A tracking number that was not purchased through EasyPost, from a carrier EasyPost does not scrape for third parties, so the Tracker returns not_found rather than events.

Tracker strategy aligned with carrier support

rate_shopping returned empty

Rate shopping returns no rates

A carrier account in verification, a parcel predefined_package the carrier does not accept, or a destination outside service area, filtering every carrier out of the response.

Rates returning across every carrier

Carrier account still needs_credentials

A carrier account will not finish onboarding

UPS or FedEx credentials that failed verification, or an address check that needs manual handling with the carrier, leaving the account unusable in rate shopping.

Carrier onboarding completed

webhook endpoint timed out at 10s

Webhook events are being dropped

A receiver that does synchronous work before responding, so EasyPost's 10-second cutoff fires and the Tracker or Shipment event is not delivered.

Webhooks responding fast and processing async

insurance declared value exceeds carrier maximum

Insured labels are being rejected

A declared value above the carrier's statutory maximum (USPS Priority tops out at $5,000, carrier-dependent beyond that), with no fallback to a supported carrier or third-party cargo insurance.

Insurance routed to a carrier that supports the value

label format mismatch

Labels are coming back in the wrong format

A request for PNG against a carrier that only returns PDF for this label type, or a ZPL request against a carrier that does not support it, so the printer pipeline rejects the asset.

Label format handled per carrier capability

Smart Rate: no delivery accuracy data

Smart Rate is missing data for some ZIPs

Rural or new-build ZIP codes where Smart Rate has not accumulated enough delivery history, so the checkout promise falls back to the carrier's default.

Checkout gracefully handling missing Smart Rate

What we do

EasyPost help, from integration rescue to a managed shipping layer

Call us when one rate call is returning empty, or hand us the whole EasyPost integration and the carrier accounts behind it.

Rescue
Trackers not firing, rate shopping empty, webhooks silently dropping. We reproduce the failure against the API and name the actual cause.
Integration build-out
Shipment, Rate, Tracker and Pickup flows built against the current EasyPost API, with retry, idempotency and error classification that will not surprise a finance team.
Carrier account onboarding
UPS, FedEx, DHL and regional carrier accounts added to EasyPost with credentials verified end-to-end so rate shopping does not quietly skip them.
Webhook consumers
Receivers that respond in milliseconds, hand off to a queue, deduplicate on Tracker and Shipment IDs, and survive the retry model that EasyPost actually uses.
Migration between EasyPost and ShipStation or ShipEngine
Comparative rate testing against real shipments, data migration for carrier accounts and tracking history, and a parallel-run plan before cutover.
Managed Tech
Daily rate shopping health, carrier onboarding watchdog, webhook delivery monitoring and an engineer to call when EasyPost or a carrier pushes a breaking change.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running EasyPost alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

EasyPost questions

Something else? Call+1 737 727 7327

Why does our EasyPost Tracker return tracker.not_found?

Trackers created against a tracking number that was not purchased through EasyPost rely on EasyPost scraping the carrier, and not every carrier is supported for third-party tracking. For domestic USPS, UPS and FedEx it usually works; for regional and international carriers it often does not, and the Tracker will return not_found rather than a partial history. We confirm what each carrier actually supports, point the application at the carrier's native tracking where EasyPost cannot help, and document the matrix so product knows what to expect.

Our rate shopping is returning no rates. Where do we look?

Start with the carrier account state. A UPS or FedEx account stuck in needs_credentials is filtered out silently. Then check the Parcel, specifically predefined_package values that one carrier accepts and another does not. Finally, the destination may be outside a carrier's service area. We walk each of those in turn, add logging that captures which carriers were considered and which were dropped, and bring the Rates list back to what it should be.

EasyPost webhooks keep dropping events. What is the pattern?

Almost always a receiver that does too much synchronously before responding. EasyPost expects a fast 2xx; a receiver that waits for a database write and a third-party call before responding will blow the timeout on a busy day. We rewrite the handler to acknowledge the event immediately and hand off to a queue, deduplicate on event ID, and backfill from the API where events were missed.

Can we rate shop across EasyPost and our own carrier contracts?

Yes. EasyPost imports your own UPS, FedEx and DHL contracts rather than forcing you onto EasyPost's negotiated rates. Once the carrier accounts are added with your credentials, rate shopping compares them alongside EasyPost's rates and your business logic picks the winner.

How do we migrate from EasyPost to ShipEngine (or vice versa)?

We rebuild the shipping layer against the target API, keep the carrier accounts active on both sides during a parallel window, run production shipments through both for a comparison period on real packages, and only then cut over. Tracking history that lives on the old side is either backfilled from the carrier directly or left on the old side with a read-only redirect.

How much does EasyPost help cost?

The estimate is on us. Describe the integration, the carriers in use and what has broken, and we respond with a price before any code is changed.

Free estimate

EasyPost giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.