Skip to main content
POST
/
v6
/
mileage
/
{mileageId}
/
route
Save route
curl --request POST \
  --url https://sandbox.tight.com/v6/mileage/{mileageId}/route \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": "mrt_12345",
  "waypoints": [
    {
      "lat": "38.8977",
      "lng": "-77.0365"
    }
  ],
  "status": "ACTIVE",
  "customData": {
    "internal_key": "some_internal_key",
    "some_other_field": 23434
  }
}
'
{
  "result": "SUCCESS",
  "data": {
    "id": "mrt_12345",
    "waypoints": [
      {
        "lat": "38.8977",
        "lng": "-77.0365"
      }
    ],
    "status": "ACTIVE",
    "customData": {
      "internal_key": "some_internal_key",
      "some_other_field": 23434
    }
  }
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, see Authentication for more detail.

Body

application/json
​
id
string

Id of the route, required when updating an existing route

Example:

"mrt_12345"

​
waypoints
object[] | null
​
status
enum<string>

Status of the route

Available options:
ACTIVE,
INACTIVE,
REMOVED
Example:

"ACTIVE"

​
customData
object

Custom JSON in which you can store any data with max length of 2000 characters

Example:
{
  "internal_key": "some_internal_key",
  "some_other_field": 23434
}

Response

Success

​
result
enum<string>

The result of the action performed.

Available options:
SUCCESS,
FAILURE
​
data
object

The data generated by the action performed.