Dangerous Goods REST API
What the API does

Consignments. The DGAssistant JSON REST API creates the dangerous goods consignment from your own management or logistics system and returns the shipper's declaration, the checklist and the package marking, already verified against the regulation that applies. Your system keeps the commercial data; DGAssistant supplies the regulatory knowledge and the documents.
Consolidation. The API also covers the grouping of consignments from several shippers, along its two axes. The contractual axis is the master consignment — a booking, a sea or air consolidation, a road groupage — with its parties, its references, the consignments attached to it, its status transitions and its history. The physical axis is the transport equipment (container, vehicle, trailer or unit load device) and the transport movement (voyage, flight or journey) with its calls, together with the vessels, vehicles and locations of the account. More than half of the service is devoted to this part.
Two ways of working: batch and interactive
Batch. A single call carries the complete specification of the consignment with all of its goods. It is the way intended for management and logistics systems that send whole shipments already assembled.
Interactive. The consignment is opened first and the goods are added one by one. Every response carries the validation messages of what has just been added, so that your own application can show them to the user while the shipment is being prepared.
Predefined data or data on the fly
Predefined data. The products and the participants — consignors, carriers, consignees, loaders and drivers — are created beforehand and the API uses their codes. It is the simplest way to work and the one we recommend, because the regulatory classification is settled once and reused in every shipment.
Data on the fly. The products and the participants are defined in the same call that creates the consignment. It suits systems that do not keep a catalogue of their own or that ship occasional goods.
The documents it returns
For each consignment: the shipper's declaration of the applicable regulation, the checklist and the package marking. They are retrieved in PDF, XLSX or DOCX, or sent directly by electronic mail from the service itself.
For consolidation: the documents of the transport unit, the documents of the movement — among them the dangerous goods manifest and the notification to the captain — and the documents of the master consignment.
What the API verifies
In the consignment. Segregation between the goods carried together, the quantity limits of the applicable packing instruction and of the limited and excepted quantity regimes, the admissibility of the goods for the mode of carriage, the legality of the packaging, and the completeness of the declaration. When something does not comply, the response states which rule is not met and with which values, so that the message can be shown in your own application.
In the consolidation. Segregation inside the transport unit, segregation between the units loaded in the same movement, the calculation of the 1.1.3.6 threshold of ADR for the movement with its breakdown, and the restrictions of the journey returned as data, such as the tunnel restriction code or the presence of high consequence dangerous goods.
Regulations and types of carriage covered
ADR for road, IMDG for sea, IATA for air and 49 CFR. The three main regulations are managed together and not as separate modules, so that a shipment that changes its mode of carriage does not have to be prepared again.
Mixed packing, overpacks, tanks, carriage in bulk, empty uncleaned packagings, waste and Class 7 radioactive material are all supported, with the data that each of them requires. The texts of the documents are issued in nineteen languages.
Availability
The service is published in three regions — Europe, the Americas and Asia-Pacific — each with its own address, so that the integration works against the region where the account is held. The infrastructure is redundant and monitored around the clock.
How to start
Request a free two week trial, and with it the credentials of the service. Authentication uses OAuth 2.0 with the client credentials grant: your system obtains an access token and sends it in every request.
The complete specification is published in OpenAPI format and can be read, explored and used to generate a client in your own language before writing a single line of integration code.