> ## Documentation Index
> Fetch the complete documentation index at: https://detrack.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Depots: Warehouse and pickup locations for Detrack routes

> A Depot is a saved warehouse or pickup location in Detrack, used as the start or end point when planning driver routes.

A **Depot** is a saved location in Detrack, typically a warehouse or dispatch hub. Depots are used as the starting point (and optionally the ending point) when planning [Routes](/concepts/routes).

## Fields

At minimum, a depot has a `name` and an `address` that can be geocoded. Detrack fills in latitude and longitude automatically.

* `name` (string, required) — Depot name, for example "Main Depot".
* `address` (string, required) — Full formatted address that Detrack can geocode.
* `addr_1`, `addr_2`, `addr_3` (string) — Optional address lines.
* `zip_code`, `city`, `state` (string) — Optional address components.
* `address_lat`, `address_lng` (float, read-only) — Coordinates set by geocoding.
* `location` (array) — Coordinates as `[longitude, latitude]`, used for map calculations.
* `id` (string, read-only) — Detrack's internal depot ID.

## Creating depots

Create a single depot with [Create depot](/api-reference/depots/create), or create up to many at once with [Bulk create](/api-reference/depots/bulk-create). Depots can be updated or deleted in bulk by name.

## Using depots in routes

When you plan a route, reference an existing depot by ID or name:

```json theme={null}
{
  "depot_location": { "id": "68f0d416e8ec54cbf4a04dba" }
}
```

You can also pass `name` and `address` instead of `id`. Detrack then saves it as a depot: it updates the depot with that name, or creates one if none exists. See [Plan a route](/api-reference/routes/plan).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.