Detrack API

Name: Detrack API
Brand: Detrack API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceShipping LogisticsapiKey23 EndpointsREST

For Agents

Create and track deliveries and collections, manage vehicles, and trigger bulk operations like reattempts in Detrack's last-mile delivery platform.

Install Jentic One Beta

Connect the Detrack API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Detrack API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Detrack API.

Create new delivery jobs with addresses, items, and time windows

Update or cancel a specific delivery by its DO number

Bulk-create or bulk-delete deliveries in a single request

Trigger reattempt jobs for failed deliveries without rebuilding them

GET STARTED

Start building with Detrack API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Detrack API, keeping it validated and agent-ready. Detrack is a delivery management and electronic proof of delivery (ePOD) platform used by last-mile logistics operators and field service teams. The API exposes deliveries, collections, vehicles, and SKU-level items so dispatchers can build job lists, track progress in real time, and handle bulk operations like reattempts. It is suited for warehouse, retail, and 3PL workflows that need programmatic control over field operations.

Use Cases

Patterns agents use Detrack API for, with concrete tasks.

★ Same-Day Dispatch Automation

Retail and grocery operators use Detrack to convert orders from their commerce platform into delivery jobs ready for the driver app. The /dn/deliveries endpoint accepts the address, time window, and item lines; the bulk variant handles end-of-day batch dispatch in one call. Most teams pair this with a webhook or polling loop to surface status updates back to the storefront.

POST /dn/deliveries/bulk with an array of 25 orders pulled from the commerce platform, then store the returned DO numbers against each order.

Failed Delivery Reattempt Workflow

When a customer is not home or refuses delivery, dispatchers need to schedule a reattempt without rebuilding the job. The /dn/deliveries/reattempt endpoint clones the original job into a new attempt with a fresh date, preserving the items and customer details. This shaves manual work off operators handling hundreds of failed deliveries per day.

POST /dn/deliveries/reattempt with the original DO number and a new date to schedule a reattempt for the next morning's route.

Reverse Logistics and Collections

Returns processing teams use the /dn/collections endpoints to schedule pickups for refunds, exchanges, or warranty returns. Collections share much of the schema with deliveries but carry their own status flow, letting ops separate outbound and inbound performance.

POST /dn/collections with the customer's pickup address and item details, then GET /dn/collections to confirm the job is scheduled.

Fleet and SKU Inventory Sync

Operations teams keep Detrack's vehicles and items aligned with their TMS or WMS by syncing fleet additions and SKU master data through the /dn/vehicles and /dn/items endpoints. This avoids drivers being assigned to retired vehicles or jobs referencing deprecated SKUs.

Loop through the WMS SKU list and PUT /dn/items/{sku} for each SKU to ensure Detrack's item catalogue matches the source-of-truth inventory.

Agent-Driven Dispatch Assistance

AI agents help dispatchers triage exceptions and schedule reattempts by calling Detrack through Jentic. The Detrack API key stays in the Jentic vault, and the agent only needs to express intent — for example, 'reattempt all deliveries that failed today' — to get the right endpoint and parameters.

Search Jentic for 'reattempt failed Detrack delivery', load the /dn/deliveries/reattempt operation, and execute it for each DO number flagged as failed.

Key Endpoints

23 endpoints — jentic publishes the only available openapi specification for detrack api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/dn/deliveries

List all deliveries

POST

/dn/deliveries

Create a delivery job

PUT

/dn/deliveries/{do_number}

Update a delivery by DO number

POST

/dn/deliveries/bulk

Bulk-create deliveries

POST

/dn/deliveries/reattempt

Reattempt a failed delivery

POST

/dn/collections

Create a collection job

POST

/dn/vehicles

Add a vehicle to the fleet

PUT

/dn/items/{sku}

Update an item by SKU

GET

/dn/deliveries

List all deliveries

POST

/dn/deliveries

Create a delivery job

PUT

/dn/deliveries/{do_number}

Update a delivery by DO number

POST

/dn/deliveries/bulk

Bulk-create deliveries

POST

/dn/deliveries/reattempt

Reattempt a failed delivery

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Detrack API key is held in the Jentic vault and injected into the apiKeyHeader on each call. Agents see no secret material; revocation is centralised through the Jentic dashboard.

Intent-based discovery

Agents search Jentic by intent (e.g. 'reattempt failed Detrack delivery') and Jentic returns the matching operation with its input schema so the agent calls /dn/deliveries/reattempt without reading Detrack docs.

Time to first call

Direct Detrack integration: 2-3 days for auth, bulk handling, and reattempt logic. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Detrack API through Jentic.

Why is there no official OpenAPI spec for Detrack API?

Detrack does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Detrack API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Detrack API use?

Detrack uses an API key sent in a request header (apiKeyHeader scheme). Through Jentic, the key is stored encrypted in the vault and injected on every call so the raw value never enters agent context.

Can I bulk-create deliveries with the Detrack API?

Yes — POST /dn/deliveries/bulk accepts an array of delivery objects and creates them in a single request, which is the recommended approach for end-of-day or scheduled dispatches over more than a handful of jobs.

How do I reattempt a failed delivery with the Detrack API?

Call POST /dn/deliveries/reattempt with the original DO number and the new attempt date. The endpoint clones the original job rather than requiring you to rebuild items and addresses.

What are the rate limits for the Detrack API?

The OpenAPI spec does not declare specific rate limits. Treat the bulk endpoints (/dn/deliveries/bulk, /dn/collections) as the safer default for high-volume workloads to reduce request count.

How do I create a delivery through Jentic?

Search Jentic for 'create a Detrack delivery', load the POST /dn/deliveries operation, and execute it with the address and item payload. Jentic injects your API key at execution and returns the new DO number.

Detrack API

Connect the Detrack API to your agent

Capabilities

Start building with Detrack API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs