FAQ
Answers for developers building with Trace.
The short version: keep your API key server-side, use one tracking endpoint, listen for signed webhooks, and keep your customer-facing tracking flow simple.
What does Trace do?
Trace turns a tracking number into a normalized shipment status, likely carrier, event timeline, cache metadata, and webhook-ready updates through one API.
How fast can I make my first tracking request?
Create an account, generate a trc_live key, and send one POST request to /v1/track. Most developers can test the API from the dashboard in under a minute.
Should I call Trace from my frontend?
No. Keep live API keys on your server. Call Trace from your backend, serverless function, worker, or private integration layer.
How do webhooks work?
Add an endpoint in the dashboard, choose the events you want, and Trace will send signed JSON payloads when tracking status changes or when you test an endpoint.
How often should I check the same shipment?
Trace caches recent lookups, so repeated requests stay fast. For active shipments, polling every few hours is usually enough; delivered shipments should stop being polled.
What carriers does Trace support?
Trace includes an 80+ carrier catalog covering major postal, courier, dropshipping, regional, and freight providers. Every carrier in the catalog is fully supported through the same API.
What happens if a carrier has no new scan?
Trace returns the latest normalized shipment state with cache metadata and a last checked time. Your app gets a predictable response even when the carrier has not posted a fresh update.
How do plans and limits work?
Plans are based on monthly lookup volume, request rate, and support needs. You can view current usage, manage your plan, and handle invoices from the dashboard.
Can I use Trace for customer-facing order tracking?
Yes. Trace is designed for order status pages, support dashboards, delivery notifications, internal operations tools, and post-purchase workflows.