Logistics & Supply Chain · Integration
Detrack
Add Detrack to your product for your customers, and give your AI agents governed access to it.
Detrack's v2 API at app.detrack.com/api/v2 authenticates with an X-API-KEY header and keys every delivery on a do_number that you supply, so the same do_number sent twice on the same date is treated as an update rather than a new job. Jobs are dated: a delivery is retrieved by do_number and date together, and omitting the date will find the wrong record once a customer reuses reference numbers across days. Proof of delivery images and signatures are not embedded in the job payload and are fetched through their own endpoint after the driver completes the stop. Status moves through values driven by the driver app rather than by your API calls, so writing a completed status from outside will be overwritten by the device. fastn holds each customer's API key, keeps do_number and date paired correctly and handles upkeep as v2 evolves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Detrack account and push delivery jobs from your order system
Create Detrack jobs from confirmed orders with the address, time window and item list already populated
Show live delivery status and driver progress inside your own customer-facing order page
Pull proof of delivery signatures and photos back into your records once a stop is marked complete
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent create or update a delivery job by do_number and date, without duplicating an existing one
Have an agent list stops that failed or were not attempted today and draft the follow-up for a dispatcher
Audit, per tenant, every job an agent created or edited in Detrack and the do_number it touched
Example prompt
Which Detrack deliveries failed yesterday, and do we have proof of delivery for the ones that completed?
Set up Detrack in 4 steps
- 01Enable the Detrack connector from your fastn dashboard.
- 02Have each customer authorise their own Detrack account, so calls run under their credentials rather than a shared key.
- 03Decide which shipments, tracking events and orders your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Detrack integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Detrack integration without building it. Your customers connect their own Detrack account inside your product and work their shipments, tracking events and orders there, with no per-customer code on your side.
- Handle the part that actually costs time: tracking data arrives from many carriers in inconsistent formats and at unpredictable times. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Detrack update is not your on-call problem.
- One integration serves your product and your agents. The same governed Detrack connection powers in-product features and gives AI agents scoped, audited access, so you keep physical movement and stock visible inside your product without wiring it twice.
Used by these teams
Compare with
AfterShip
EasyPost
Cin7Often used alongside
Tools the same teams tend to run next to Detrack, across other categories.
NetSuite
Shopify
Stripe
QuickBooksDetrack integration FAQ
How do I add a Detrack integration to my product?
Enable the Detrack connector in your fastn dashboard, then let each customer authenticate their own Detrack account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Detrack client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Detrack account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Detrack account and only ever sees their own shipments, tracking events and orders. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Detrack integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent create or update a delivery job by do_number and date, without duplicating an existing one
Who maintains the Detrack integration?
fastn does. When Detrack changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I track shipments from Detrack inside my product?
Yes. Shipment and tracking events are read per customer and can trigger your workflows, so status changes surface in your product instead of your users checking a carrier site.
What does my product get back from Detrack as things move?
Whatever Detrack actually holds. Where it moves goods, that is shipment and tracking events, read per customer and delivered as they land. Where it holds stock, levels can be read on demand or kept in step through events, so your product is not deciding on a stale count. Where it carries orders and documents between trading partners, it is the acknowledgement, ship notice or status change that says what moved.
What can I build with the Detrack integration?
A common starting point: let a customer connect their own Detrack account and push delivery jobs from your order system. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Detrack integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Detrack does not change your per-connector cost. You can start free with 3 connected accounts.
Add Detrack to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.