Transport Messages
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/"
1f527452-45f4-11eb-a722-0242ac140004Date of creation on our server
2020-12-22T15:31:39.26167ZFilename or if uploaded by a trucker from the mobile app, the document title is generic, for instance photo.
delivery_note_2105_001File content. Use content-type with multipart/form-data value to the header of the request to send a document.
This field is used for the default values of the field readable_by_company_ids; if null, companies from all Sites of the transport are listed in readable_by_company_ids, otherwise only the company of this Site. Site must exist in this transport. This field is part of a beta feature.
6d95e434-146c-4b8d-a99c-7ef908238445A list containing the pk of each company allowed to access the document, every company must be part of the transport. If no values are sent, it will be computed with default values; Carrier, Shipper, Invoiced Customer and Site's pk (see Site field). Once values have been sent, the behavior adding default companies is deactivated. The author company is always added. Only pks of companies from the transport will be added, others will be ignored. This field is part of a beta feature.
[1, 2, 3, 4]message displayed in the activity thread of a transport in the web app and in the mobile app
Latitude using the decimal GPS coordinates (WGS84). At 7 decimals, the position is accurate around the centimeter.
-52.5561625Longitude using the decimal GPS coordinates (WGS84). At 7 decimals, the position is accurate around the centimeter.
92.896504Free text. This reference is searchable in the transports dashboard.
delivery note 123456 client 1This field is used to make the transport message public, which makes it visible by all parties of the transport.
This field is used to allow truckers to see the transport message. Only available for carriers.
Create successful
1f527452-45f4-11eb-a722-0242ac140004Date of creation on our server
2020-12-22T15:31:39.26167ZFilename or if uploaded by a trucker from the mobile app, the document title is generic, for instance photo.
URL of the stored document. You can download the document from this URL.
https://storage.googleapis.com/dashdoc-media/media/shipments/aabd42eb.pngThis field is used for the default values of the field readable_by_company_ids; if null, companies from all Sites of the transport are listed in readable_by_company_ids, otherwise only the company of this Site. Site must exist in this transport. This field is part of a beta feature.
6d95e434-146c-4b8d-a99c-7ef908238445A list containing the pk of each company allowed to access the document, every company must be part of the transport. If no values are sent, it will be computed with default values; Carrier, Shipper, Invoiced Customer and Site's pk (see Site field). Once values have been sent, the behavior adding default companies is deactivated. The author company is always added. Only pks of companies from the transport will be added, others will be ignored. This field is part of a beta feature.
[1, 2, 3, 4]message displayed in the activity thread of a transport in the web app and in the mobile app
Latitude using the decimal GPS coordinates (WGS84). At 7 decimals, the position is accurate around the centimeter.
-52.5561625Longitude using the decimal GPS coordinates (WGS84). At 7 decimals, the position is accurate around the centimeter.
92.896504Free text. This reference is searchable in the transports dashboard. Filled by trucker if document is added from mobile app, by user if document is added from web app, or filled by API request.
delivery note 123456 client 1This field is used to make the transport message public, which makes it visible by all parties of the transport.
This field is used to allow truckers to see the transport message. Only available for carriers.
Create successful
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/"
Empty body
Empty body
No content
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/"
Get successful
Get successful
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/"
1f527452-45f4-11eb-a722-0242ac140004Date of creation on our server
2020-12-22T15:31:39.26167ZFilename or if uploaded by a trucker from the mobile app, the document title is generic, for instance photo.
This field is used for the default values of the field readable_by_company_ids; if null, companies from all Sites of the transport are listed in readable_by_company_ids, otherwise only the company of this Site. Site must exist in this transport. This field is part of a beta feature.
6d95e434-146c-4b8d-a99c-7ef908238445A list containing the pk of each company allowed to access the document, every company must be part of the transport. If no values are sent, it will be computed with default values; Carrier, Shipper, Invoiced Customer and Site's pk (see Site field). Once values have been sent, the behavior adding default companies is deactivated. The author company is always added. Only pks of companies from the transport will be added, others will be ignored. This field is part of a beta feature.
[1, 2, 3, 4]message displayed in the activity thread of a transport in the web app and in the mobile app
Latitude using the decimal GPS coordinates (WGS84). At 7 decimals, the position is accurate around the centimeter.
-52.5561625Longitude using the decimal GPS coordinates (WGS84). At 7 decimals, the position is accurate around the centimeter.
92.896504Free text. This reference is searchable in the transports dashboard. Filled by trucker if document is added from mobile app, by user if document is added from web app, or filled by API request.
delivery note 123456 client 1This field is used to make the transport message public, which makes it visible by all parties of the transport.
This field is used to allow truckers to see the transport message. Only available for carriers.
Update successful
Update successful
Last updated
Was this helpful?