ShipEngine has been rebranded as ShipStation API. Its official references distinguish that standalone API from other ShipStation API versions, so begin by identifying the exact product and base URL in your application.
Trace is an alternative tracking layer, not a replacement for shipping rates, labels and address validation. Evaluate whether its tested parcel results and order-linked resources justify maintaining a separate integration.
Identify the API before comparing features
The official ShipStation API overview separates the formerly ShipEngine standalone API from the app’s other API versions. The rebrand does not mean every ShipStation route or account has the same contract. Match your existing endpoints, carrier configuration and entitlement to the correct reference.
Trace uses one public base URL and account API keys for tracking and owned shipment resources. Its accepted carrier catalog is not a list of proven live integrations. Before switching, test the actual carriers and destinations in your operating environment rather than assuming nominal catalog parity.
| Requirement | Trace API | ShipEngine / ShipStation API |
|---|---|---|
| Shipping labels and rates | Not provided | Official getting-started documentation includes labels and rates. |
| External parcel tracking | Requires usable events from a configured source | Official tracking reference supports external labels with stated requirements. |
| Carrier configuration | Send a catalog carrier code when known or ambiguous | Tracking reference specifies carrier_code and connection requirements. |
| Update subscription | Owned records support best-effort monitoring | The documented tracking/start workflow subscribes to updates. |
| Order records | order_id, reference, metadata and parcel-cycle idempotency | Evaluate the relevant API version’s resource model. |
| Commercial fit | Free lookup budget; paid checkout currently disabled | Check the current plan and carrier entitlements for the correct API product. |
Three reasons to retain, combine or replace the tracking layer
Retain: a warehouse uses the shipping API for labels, rating and carrier accounts, and its existing tracking subscription satisfies the required lanes. Adding another provider may create more mapping work without improving the buyer’s experience.
Combine: a marketplace receives labels from several seller systems and wants one local order projection. It can evaluate Trace for the tracking-data layer while keeping its shipping API for the operations it already performs well. That combination still needs explicit provenance and measured source behavior.
Replace tracking only: a custom application wants separate owned parcel-cycle records and transparent freshness handling. Pilot those requirements against Trace and the existing subscription before changing customer traffic. Do not switch label purchasing or carrier credentials as an incidental part of that pilot.
Map carrier codes, resources and timestamps explicitly
Keep your shipping label ID, provider tracking reference, carrier number and marketplace order ID separately. A label identifier is not a carrier tracking number. Create a Trace record for the intended parcel cycle and save its ID alongside the existing provider reference.
Translate carrier codes through a tested mapping. Do not assume codes from one API are portable strings in another. Preserve source status descriptions when a broader provider vocabulary does not fit Trace’s six normalized states, and identify records without verified scans instead of assigning them an in-transit default.
Where Trace cannot verify a timezone, it retains the source-local timestamp with explicit metadata. Your consumer must support null UTC timestamps. This is especially relevant when a logistics dashboard calculates stalled ages or transit durations from imported histories.
- Inspect the exact API version and plan used by the shipping integration.
- Qualify a real cohort of the carriers and destinations you intend to move.
- Create idempotent Trace records and compare resource IDs, latest scans and failure outcomes.
- Run notification handling on one authoritative projection to avoid duplicate customer updates.
Treat subscription and receiver failure as operational workflows
Test when tracking subscriptions begin and end under the existing provider’s documented contract. Separately, Trace’s shipment monitoring is best effort for up to 30 days and roughly six-hour refresh intervals after successful checks. A receiver’s reachability and a carrier source’s availability are different failure modes.
For Trace events, use a final HTTPS receiver, raw-body verification and durable event-ID deduplication. Inspect saved attempts after authentication errors or transient failures. Explicit replay preserves event identity and requires a reason; it is not a way to bypass receiver authentication or recreate missing carrier evidence.
Choose with a representative pilot and complete cost estimate
Estimate successful lookup usage across the intended parcel lifetime, including cache hits and background refreshes. Then include the implementation and support work for a separate tracking provider. Trace’s free allowance is useful for development, but it is not unlimited production monitoring and paid checkout remains disabled in this release.
Compare verified-result rate, source freshness, recovery completeness and the required shipping features. The official references below support the product distinctions; they do not establish that Trace is faster, cheaper or equally broad. Keep the current provider if those tested requirements are not met.
A successful migration is one where the application’s data model becomes clearer and its measured operating behavior improves. The rebrand alone is not a reason to replace a working shipping API.
Common questions
Is ShipEngine now ShipStation API?
Yes. The official rebrand announcement and API overview explain the naming change. Identify the exact API version and base URL before applying migration advice.
Does Trace require moving my label purchases?
No. Trace does not purchase labels. Evaluate a tracking-only change separately from your shipping workflow.
Can a carrier code be copied directly between providers?
Do not assume that. Map the provider’s identifier to a Trace catalog code and validate the real parcel cohort.
References & next steps
Implementation details were checked against Trace’s current API. External product details may change; verify the linked documentation before deciding.