Skip to content

Adds a new Route

Request

Security
BearerToken
Bodyapplication/json
entityTypestring
Value:"route"
Example:"route"
idstring

Uniquely identifies this entity. A URI can be assigned by the client to indicate where more information can be retrieved. Note that every entity always has a unique EntityId. However since, OTM5.2 it is not required to send it in the request. One can be generated for you by the server.

Example:"beb9a25f-3f64-42ae-b1c6-e89cd450f66b"
namestring

Name of the entity. For display purposes and search only.

Example:"An example route using coordinates to indicate how to drive."
creationDatestring, (date-time)

The creation date of this entity.

lastModifiedstring, (date-time)

The last modified date of this entity. If none is given the creation date is used instead.

contextEventsArray of any(event)

The context events provides some optional information about the events that can provide additional information on the current state of this entity.

For example: your system might send ETA information for the arrival of a vehicle on a location. To make it clear what caused this ETA to be updated, we can include some information about what caused this ETA update by including an event as context. If your ETA update was caused by a location update, this event can be included as context. If the ETA was caused by a traffic accident on the route of the vehicle, you can include that event in the context.

externalAttributesobject

External attributes are a simple way to add information in an OpenTripModel message that could not fit into one of the OTM fields otherwise. The externalAttributes member is meant for additional meta data and/or additional ID's of an entity. This can also help to identify an OTM entity in a system by the ID of that system.

Please, use this with caution: having too many external attributes can be a sign of not using OpenTripModel as it was intended.

externalIdentifiersArray of objects(externalIdentifiers)

Standardized identifiers of this entity as known in external systems. Use this to exchange repeatable partner or system specific identifiers without overloading externalAttributes.

Example:
[
  {
    "id": "AAA",
    "scheme": "CAS"
  }
]
geoReferenceany(geoReference)required
Example:
{
  "geometry": {
    "coordinates": [ … ],
    "type": "LineString"
  },
  "type": "Feature"
}
geoReferencesany(geoReference)
actorsArray of any

Actors associated with this route, for instance the Company that requires this route as a Last-Mile guidance.

constraintany
curl -i -X PUT \
  https://otm-api-spec.redocly.app/_mock/api/5.9/otm/api/v5/routes \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "id": "beb9a25f-3f64-42ae-b1c6-e89cd450f66b",
    "name": "An example route using coordinates to indicate how to drive.",
    "geoReference": {
      "geometry": {
        "coordinates": [
          [
            1,
            0
          ],
          [
            5,
            0
          ],
          [
            5,
            3
          ],
          [
            13,
            3
          ],
          [
            13,
            7
          ]
        ],
        "type": "LineString"
      },
      "type": "Feature"
    }
  }'

Responses

The same entity

Bodyapplication/json
entityTypestring
Value:"route"
Example:"route"
idstring

Uniquely identifies this entity. A URI can be assigned by the client to indicate where more information can be retrieved. Note that every entity always has a unique EntityId. However since, OTM5.2 it is not required to send it in the request. One can be generated for you by the server.

Example:"beb9a25f-3f64-42ae-b1c6-e89cd450f66b"
namestring

Name of the entity. For display purposes and search only.

Example:"An example route using coordinates to indicate how to drive."
creationDatestring, (date-time)

The creation date of this entity.

lastModifiedstring, (date-time)

The last modified date of this entity. If none is given the creation date is used instead.

contextEventsArray of any(event)

The context events provides some optional information about the events that can provide additional information on the current state of this entity.

For example: your system might send ETA information for the arrival of a vehicle on a location. To make it clear what caused this ETA to be updated, we can include some information about what caused this ETA update by including an event as context. If your ETA update was caused by a location update, this event can be included as context. If the ETA was caused by a traffic accident on the route of the vehicle, you can include that event in the context.

externalAttributesobject

External attributes are a simple way to add information in an OpenTripModel message that could not fit into one of the OTM fields otherwise. The externalAttributes member is meant for additional meta data and/or additional ID's of an entity. This can also help to identify an OTM entity in a system by the ID of that system.

Please, use this with caution: having too many external attributes can be a sign of not using OpenTripModel as it was intended.

externalIdentifiersArray of objects(externalIdentifiers)

Standardized identifiers of this entity as known in external systems. Use this to exchange repeatable partner or system specific identifiers without overloading externalAttributes.

Example:
[
  {
    "id": "AAA",
    "scheme": "CAS"
  }
]
geoReferenceany(geoReference)required
Example:
{
  "geometry": {
    "coordinates": [ … ],
    "type": "LineString"
  },
  "type": "Feature"
}
geoReferencesany(geoReference)
actorsArray of any

Actors associated with this route, for instance the Company that requires this route as a Last-Mile guidance.

constraintany
Response
{
  "id": "beb9a25f-3f64-42ae-b1c6-e89cd450f66b",
  "name": "An example route using coordinates to indicate how to drive.",
  "geoReference": {
    "geometry": { … },
    "type": "Feature"
  }
}