Forms
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/"
A page number within the paginated result set.
Filter waste forms by uid
Filter waste forms by creation date
Filter waste forms created after a certain date
Filter waste forms created on or after a certain date
Filter waste forms created before a certain date
Filter waste forms created on or before a certain date
The status of the waste shipment
completedPossible values: Filter waste forms by multiple statuses, comma separated
cancelled,discontinuedGet 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/"
The ID of the producer company. You need to have the company created first with the /v4/companies/ endpoint. Make sure you also set the specific details that are mandatory for waste activity with the endpoint /v4/wam/companies/{id}/details/.
1The ID of the processor company. You need to have the company created first with the /v4/companies/ endpoint. Make sure you also set the specific details that are mandatory for waste activity with the endpoint /v4/wam/companies/{id}/details/.
2The ID of the carrier company. You need to have the company created first with the /v4/companies/ endpoint. Make sure you also set the specific details that are mandatory for waste activity with the endpoint /v4/wam/companies/{id}/details/.
3The ID of the organizer company. You need to have the company created first with the /v4/companies/ endpoint. Make sure you also set the specific details that are mandatory for waste activity with the endpoint /v4/wam/companies/{id}/details/.
4The ID of the origin address. If it does not exist, create it first with the /v4/addresses/ endpoint.
5The ID of the destination address. If it does not exist, create it first with the /v4/addresses/ endpoint. Deprecated because it is no longer used. We now use the processor address as destination.
6Handle with careName of the sea ship
Sea ship nameIMO number of the sea ship
IMO1234567MMSI number of the sea ship
123456789ENI number of the sea ship
123456782022-01-01T00:00:00ZThe UID of the carrier contact. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000The UID of the organizer signatory. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000The UID of the producer contact. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000The UID of the processor contact. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000The UID of the processor signatory. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000Create successful
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/"
Unique identifier of the waste form
A waste form cannot be deleted, but cancelling or discontinuing it is allowed from the web app
A waste form cannot be deleted, but cancelling or discontinuing it is allowed from the web app
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/"
Unique identifier of the waste form
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/"
Unique identifier of the waste form
The ID of the producer company. You need to have the company created first with the /v4/companies/ endpoint. Make sure you also set the specific details that are mandatory for waste activity with the endpoint /v4/wam/companies/{id}/details/.
1The ID of the processor company. You need to have the company created first with the /v4/companies/ endpoint. Make sure you also set the specific details that are mandatory for waste activity with the endpoint /v4/wam/companies/{id}/details/.
2The ID of the carrier company. You need to have the company created first with the /v4/companies/ endpoint. Make sure you also set the specific details that are mandatory for waste activity with the endpoint /v4/wam/companies/{id}/details/.
3The ID of the organizer company. You need to have the company created first with the /v4/companies/ endpoint. Make sure you also set the specific details that are mandatory for waste activity with the endpoint /v4/wam/companies/{id}/details/.
4The ID of the origin address. If it does not exist, create it first with the /v4/addresses/ endpoint.
5The ID of the destination address. If it does not exist, create it first with the /v4/addresses/ endpoint. Deprecated because it is no longer used. We now use the processor address as destination.
6Handle with careName of the sea ship
Sea ship nameIMO number of the sea ship
IMO1234567MMSI number of the sea ship
123456789ENI number of the sea ship
123456782022-01-01T00:00:00ZThe UID of the carrier contact. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000The UID of the organizer signatory. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000The UID of the producer contact. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000The UID of the processor contact. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000The UID of the processor signatory. If it does not exist, create it first with the /v4/wam/contacts/ endpoint.
123e4567-e89b-12d3-a456-426614174000Update successful
Update successful
Last updated
Was this helpful?