# Detrack integrations: jobs, job exports and depots

> Create a job, export jobs in bulk and create a depot in Detrack. Connect Detrack to the rest of your supply chain stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/detrack-integrations/
**Categories:** Supply chain
**Connects through:** HTTP Connector

## Overview

Detrack is delivery management software that dispatches delivery and collection jobs to drivers, plans routes, and records proof of delivery. Tray.ai connects to Detrack through the HTTP Connector, so your workflows can call the Detrack API alongside the rest of your stack.

## Use cases

### Jobs

Read, create, update, and delete jobs in Detrack from any Tray.ai workflow. The Detrack API covers calls such as list jobs and create a job.

- List jobs
- Create a job
- Create jobs in bulk

### Job exports

Read job exports in Detrack from any Tray.ai workflow. The Detrack API covers calls such as export jobs in bulk and get export status.

- Export jobs in bulk
- Get export status
- Download an exported job

### Depots

Read, create, update, and delete depots in Detrack from any Tray.ai workflow. The Detrack API covers calls such as list depots and create a depot.

- List depots
- Create a depot
- Update depots in bulk

### Routes

Read and create routes in Detrack from any Tray.ai workflow. The Detrack API covers calls such as list routes by date and get a route by name.

- List routes by date
- Get a route by name
- Create or update a route

## Challenges Tray.ai solves

### Keeping Detrack credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Detrack credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Detrack API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Detrack API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Detrack?

Yes. Tray.ai connects to Detrack through the HTTP Connector, which calls the Detrack API directly. Any call the Detrack API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Detrack?

The Detrack API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Detrack connector?

Detrack runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Detrack connector from the Detrack API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/