About Trace
Trace API, explained.
Trace is a package tracking API for developers building order visibility, support workflows and parcel timelines. It is separate from software observability or distributed-tracing APIs that also use the word “trace.”
One tracking layer for your application
Trace supplies normalized shipment events when a configured source returns usable data for the requested number. Applications can create order-linked parcel records, use best-effort monitoring, inspect exception actions, import records and investigate webhook deliveries. The customer interface and business decisions remain with the application.
It does not purchase shipping labels, rate-shop shipments or install a native Shopify or WooCommerce app. An accepted carrier code is not a guarantee of live source coverage.
Make the evidence and its limits visible
Verification here means that the parser found dated events associated with the requested parcel on a source page. It is not independent carrier-authoritative confirmation. Important or disputed delivery claims should be checked against the carrier’s own evidence.
Responses preserve verification age, explicitly identify stale fallback data, and retain usable local scan times when a timezone cannot be established. Source failures remain errors rather than fabricated shipment movement.
Documentation maintained with the product
The use-case, comparison and developer guides are maintained by Trace. They distinguish currently shipped capabilities from application patterns and retain links to primary external references. Comparisons disclose that they are written by Trace; prices, carrier behavior and third-party features should be rechecked when evaluating an integration.
Our status page reports service readiness and sampled observations, not continuous externally measured uptime or coverage for every carrier. The free plan provides 200 monthly lookups. Paid checkout is disabled in the current release.
Get a concrete answer for your workflow
For integration support, include a request ID or delivery ID and a description of the expected behavior. Keep live API keys and webhook signing secrets out of support messages. For coverage evaluation, describe the relevant carrier and destination rather than relying on a catalog count alone.