---
title: 'GET /route/directions'
description: 'Get turn-by-turn directions'
---

# GET /route/directions

Get turn-by-turn directions

| Detail | Value |
|---|---|
| Operation ID | `route.directions` |
| Method | `GET` |
| Path | `/route/directions` |
| Connector | [Radar](./) |

## Parameters

| Name | Location | Type | Required |
|---|---|---|---|
| `locations` | query | string | **Yes** |
| `mode` | query | string | No |
| `units` | query | string | No |
| `avoid` | query | string | No |
| `lang` | query | string | No |

## Using this endpoint in a workflow

1. Add an **API Call** node to your workflow.
2. Pick your Radar connection from the Connection dropdown.
3. In the Operation dropdown, select `route.directions`.
4. Fill in the parameter fields that appear. Use `{{...}}` to reference upstream values.

**Required fields are marked — fill them or the call will fail at runtime.**

## What it returns

The `API Call` node writes the response to the workflow context:

```
{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}
```

Reference response fields downstream as <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream Radar API reference.