Track Dechets
List TrackDéchets waste notes linked to your transports
transport uid
4443d4b6-e165-11ea-a488-0242ac110007
transport remote_id
. You can use the remote_id
of the transport (coming from your system), instead of its uid coming from Dashdoc, to filter this query
any_id
GET /api/v4/track-dechets/ HTTP/1.1
Host: api.dashdoc.eu
Authentication: YOUR_API_KEY
Accept: */*
Get successful
{
"count": 1,
"next": "text",
"previous": "text",
"results": [
{
"uid": "123e4567-e89b-12d3-a456-426614174000",
"readable_id": "BSD-20220408-Q4AMB20ZE",
"opaque_id": "cl1q5rr1o1373321fwze3n198tk",
"status": "DRAFT",
"type": "BSD",
"transport": {
"uid": "d6e95574-8c1f-4b97-bdea-f20d0eb4f7f0",
"remote_id": "TRANSP_123456"
},
"created": "2025-06-26T19:25:47.624Z",
"updated": "2025-06-26T19:25:47.624Z"
}
]
}
Link a TrackDéchets waste note to a transport. The waste note should exist on TrackDéchets (check is performed before link is created).
Waste note readable id from TrackDéchets
BSD-123-456
POST /api/v4/track-dechets/ HTTP/1.1
Host: api.dashdoc.eu
Authentication: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 116
{
"readable_id": "BSD-123-456",
"transport": {
"uid": "d6e95574-8c1f-4b97-bdea-f20d0eb4f7f0",
"remote_id": "TRANSP_123456"
}
}
Create successful
{
"uid": "123e4567-e89b-12d3-a456-426614174000",
"readable_id": "BSD-20220408-Q4AMB20ZE",
"opaque_id": "cl1q5rr1o1373321fwze3n198tk",
"status": "DRAFT",
"type": "BSD",
"transport": {
"uid": "d6e95574-8c1f-4b97-bdea-f20d0eb4f7f0",
"remote_id": "TRANSP_123456"
},
"created": "2025-06-26T19:25:47.624Z",
"updated": "2025-06-26T19:25:47.624Z"
}
uid of the association. You can find it in the response of the POST request for association creation
DELETE /api/v4/track-dechets/{uid}/ HTTP/1.1
Host: api.dashdoc.eu
Authentication: YOUR_API_KEY
Accept: */*
Empty body
No content
uid of the association
If you choose to identify an object with its readable_id
from TrackDechets instead of its uid
then
-
replace the
uid
value with thereadable_id
value in the URL -
specify
lookup_field=readable_id
in the query parameters
Used to specify what field is used in the URL to identify the object you're requesting, e.g. with the readable_id
(see path parameters)
GET /api/v4/track-dechets/{uid}/ HTTP/1.1
Host: api.dashdoc.eu
Authentication: YOUR_API_KEY
Accept: */*
Get successful
{
"uid": "123e4567-e89b-12d3-a456-426614174000",
"readable_id": "BSD-20220408-Q4AMB20ZE",
"opaque_id": "cl1q5rr1o1373321fwze3n198tk",
"status": "DRAFT",
"type": "BSD",
"transport": {
"uid": "d6e95574-8c1f-4b97-bdea-f20d0eb4f7f0",
"remote_id": "TRANSP_123456"
},
"created": "2025-06-26T19:25:47.624Z",
"updated": "2025-06-26T19:25:47.624Z"
}
Last updated
Was this helpful?