01 / Visual timeline builder
Make the journey yours.
Choose a theme, layout, density and language. Preview real components with local scenarios, then copy the React example.
Open the builderA clearer journey,
from your first line.
Useful components and tools for the experience after checkout. Bring any provider, try local data, and make the result your own.
No account for local tools · MIT toolkit · No hidden component telemetry
Browse the reusable template gallery02 / JSON validator & adapter playground
Understand your data.
Paste a canonical shipment or Trace response locally. Find invalid dates and unclear freshness before that data reaches a customer.
Validate local JSON03 / Shipment scenario simulator
Practice the difficult updates.
Explore delivery, exceptions, stale data and unknown timezones. Local fixtures let you design without a carrier connection.
Explore the scenarios04 / Durable Next.js order starter
From order to signed update.
Start with fictional parcels, then follow the documented private-order and webhook setup. Inspect duplicate, replay and restart behavior locally.
Get the order starterWebhook doctor · Local CLIInspect the bytes.
Inspect the bytes.
Find the next step.
Run generated signature fixtures or get an explanation for a receiver status. Verify a saved raw body privately with an environment secret. The tool makes no network requests and never prints your payload or secret.
Signature verification checks authenticity. It does not prove that a parcel moved or an event finished processing.
Terminal · from the public toolkit
git clone https://github.com/traceapi-dev/trace-ui.git
cd trace-ui
node tools/webhook-doctor.mjs self-test
node tools/webhook-doctor.mjs status 401
# For an actual saved delivery, set TRACE_WEBHOOK_SECRET
# privately, then use the unchanged raw body and header:
node tools/webhook-doctor.mjs verify body.json signature.txt