Segments

Partially update a segment

patch
Authorizations
AuthenticationstringRequired

Authentication is token based. You can issue a token for your API request from the 'API' section of the settings menu. The token MUST be sent in a Authorization header with each request.

Example of authenticated request

$ curl -X GET -H "Authorization: Token <your token>" "https://api.dashdoc.eu/api/v4/"
Path parameters
uidstringRequired
remote_idstringOptional

If you choose to identify an object with its remote_id instead of its uid then

  • replace the uid value with the remote_id value in the URL

  • specify lookup_field=remote_id in the query parameters

Query parameters
lookup_fieldstringOptional

Used to specify what field is used in the URL to identify the object you're requesting, e.g. with the remote_id (see path parameters)

Body
remote_idstringOptional

The id of the segment in your system.

scheduled_startstringOptionalDeprecated

The scheduled date and time of arrival at the origin (ISO 8601)

scheduled_endstringOptionalDeprecated

The scheduled date and time of arrival at the destination (ISO 8601)

Responses
200

Update successful

application/json
uidstring · min: 1Optional
remote_idstring · min: 1Optional
sort_ordernumberOptional

The index of the segment in the transport

Example: 0
scheduled_startstringOptionalDeprecated

The datetime at which the carrier scheduled the start of this segment

scheduled_endstringOptionalDeprecated

The datetime at which the carrier scheduled the end of this segment

telematic_distanceintegerOptional

Automatically computed distance from telematic data (in kms).

distanceintegerOptional

Manually entered distance. If null, it takes the value of telematic_distance (in kms).

origin_mileageintegerOptional

Mileage at transport origin site (in kms).

destination_mileageintegerOptional

Mileage at transport destination site (in kms).

patch
/segments/{uid}/
200

Update successful

Last updated

Was this helpful?