Get the details of a planned route identifier using its id
or external_id
.
This endpoint uses query paramsInstead of sending a payload, include the
id
orexternal_id
in the endpoint URL. For example:
https://developer-api.bringg.com/services/<service-id>/<secret-1>/<secret-2>/?id=12345
https://developer-api.bringg.com/services/<service-id>/<secret-1>/<secret-2>/?external_id=v123
Response (Output) Params
Parameter | Description |
---|---|
* | Indicates whether the service completed successfully.
|
* | If an error occurred, a message indicating the error is included. |
* | If an error occurred, the return code is included. |
* | The timestamp when the user was created. This is in UTC and the format is "%Y-%m-%dT%H:%M:%S%z". |
* | Your system's ID for this planned route identifier. |
* | Your system's ID for the team to which this planned route identifier is assigned. |
* | The Bringg ID for this planned route identifier. |
* | Indicates the hierarchy among your route identifiers. The route identifier with the highest priority receives the route scheduled to leave first. |
* | Bringg's ID for the team to which this planned route identifier is assigned. |
* | The title of the planned route identifier as it appears in the Bringg UI (for example, in the Route Name column). |
* | The last date and time this team was updated. This is in UTC and the format is "%Y-%m-%dT%H:%M:%S%z". |