> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/tracking/route/index.md).

# Getting route

API call for getting the route to destination point.

## API actions

API path: `/route`.

### get

Gets route points via specified route provider.

#### Parameters

| name           | description                                                                                                      | type                                                        |
| -------------- | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| start          | Location JSON object. Start of route.                                                                            | JSON object                                                 |
| end            | Location JSON object. End of route.                                                                              | JSON object                                                 |
| waypoints      | Optional. List of transitional points. `[{locationA},{locationN}]`.                                              | array of JSON objects                                       |
| point\_limit   | Optional. If specified, the returned route will be simplified to contain this number of points (or less). Min=2. | int                                                         |
| provider\_type | Optional. If not specified, the default user provider is used. One of "progorod", or "google", "osrm".           | [enum](/docs/navixy-api/user-api/backend-api.md#data-types) |

* `location` object described in [data types description section](/docs/navixy-api/user-api/backend-api.md#data-types).

#### Example

cURL

{% code overflow="wrap" %}

```sh
curl -X POST 'https://api.eu.navixy.com/v2/route/get' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "start": {"lat": 34.178868, "lng": -118.599672}, "end": {"lat": 31.738386, "lng": -106.453854}}'
```

{% endcode %}

#### Response

```json
{
  "success": true,
  "distance": 1340584,
  "time": 43500,
  "list": [
    {
      "lat": 34.178868,
      "lng": -118.599672
    },
    {
      "lat": 31.738386,
      "lng": -106.453854
    }
  ],
  "key_points": [
    {
      "id": 123,
      "lat": 35.365948,
      "lng": -108.112104
    }
  ]
}
```

* `distance` - int. Length in meters.
* `time` - int. Duration in seconds.
* `list` - list of route points. Location objects.
* `key_points` - list of points corresponding to `start` point, `waypoints` and `end` point (in that sequence).
  * `id` - int. index in points `list`.
  * `lat` - float. Latitude.
  * `lng` - float. Longitude.

#### Errors

* 215 - External service error.
* 218 - Malformed external service parameters.
* 236 - Feature unavailable due to tariff restrictions – if there is at least one tracker without "routing" tariff feature.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://navixy.com/docs/navixy-api/user-api/backend-api/resources/tracking/route/index.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.