Deliveries

Dangerous Goods

View as Markdown

Dangerous Goods (DGs) are declared at the parcel level when creating a delivery. Each parcel that contains dangerous goods must include contains_dangerous_goods: true and a dangerous_goods object with, at minimum, a reference to a pre-configured Dangerous Goods Definition.

For an overview of how DG Definitions work and the two integration approaches (definition-only vs. field overrides), see Dangerous Goods in the Key Concepts section.

Endpoint

POST {{domain}}/{{tenant_id}}/deliveries

Authentication: Bearer token required via the Authorization header.

Minimal Example — Using a Definition

Parcels — Minimal DG Example
1"parcels": [
2    {
3        "reference": "PARCEL_001",
4        "type": "carton",
5        "description": "BOX A",
6        "length_cm": 20,
7        "width_cm": 20,
8        "height_cm": 20,
9        "weight_kg": 2,
10        "quantity": 2,
11        "contains_dangerous_goods": true,
12        "dangerous_goods": {
13            "dangerous_goods_definition": "ap_standard_parcels"
14        }
15    }
16]

Full Example — With Field Overrides

Parcels — Full DG Example with Overrides
1"parcels": [
2    {
3        "reference": "PARCEL_002",
4        "type": "carton",
5        "description": "BOX B",
6        "length_cm": 20,
7        "width_cm": 20,
8        "height_cm": 20,
9        "weight_kg": 2,
10        "quantity": 1,
11        "contains_dangerous_goods": true,
12        "dangerous_goods": {
13            "dangerous_goods_definition": "dangerous_goods_1",
14            "dangerous_goods_declaration": "UN2910_radioactive_excepted_limited_qty",
15            "class_division": 2,
16            "packing_group_designator": "III",
17            "un_number": 1950,
18            "technical_name": "technical name",
19            "net_weight_kg": 2,
20            "outer_packaging_type": "carton",
21            "outer_packaging_quantity": 1
22        }
23    }
24]

Parcel-Level DG Fields

The following fields are added to each parcel object when shipping dangerous goods.

FieldRequiredTypeDescription
contains_dangerous_goodsNoBooleanIndicates the parcel contains dangerous goods. When true, the dangerous_goods object is required. Defaults to false.
dangerous_goodsNoObjectThe dangerous goods details for this parcel. Required when contains_dangerous_goods is true.

Dangerous Goods Object Fields

FieldRequiredTypeDescription
dangerous_goods_definitionYesStringThe name of a pre-configured Dangerous Goods Definition for your account (e.g. ap_standard_parcels). This resolves all required DG fields automatically. Other fields in this object are optional and will override the definition values if provided.
dangerous_goods_declarationNoStringA carrier pre-configured dangerous goods declaration identifier, where applicable.
transportable_by_airNoBooleanWhether the dangerous good is permitted to be transported by air.
un_numberNoNumberThe UN number identifying the dangerous good (e.g. 1950 for aerosols).
technical_nameNoStringThe UN technical shipping name of the dangerous good.
net_weight_kgNoNumberThe net weight of the dangerous goods in kilograms.
class_divisionNoNumberThe hazard class or division of the dangerous good (e.g. 2 for gases).
subsidiary_riskNoNumberThe subsidiary risk class, where the dangerous good has a secondary hazard classification.
packing_group_designatorNoEnumThe packing group based on the degree of danger. Must be one of: I, II, III.
outer_packaging_typeNoStringThe outer packaging type for the shipment. Standard values: carton, satchel, pallet, skid, jiffy, bag. Contact Rendr for specific requirements outside these options.
outer_packaging_quantityNoNumberThe number of outer packaging units.

The preferred integration approach is to use dangerous_goods_definition without overrides wherever possible. Definitions are agreed and validated during onboarding, ensuring compliance is enforced at the configuration level. Override fields should only be used where a shipment genuinely falls outside the scope of an existing definition.

Manifesting Dangerous Goods

Where DG and non-DG parcels must be manifested separately, include contains_dangerous_goods: true in the Create Manifest request. A separate manifest call with contains_dangerous_goods: false is required to manifest the non-DG parcels.

POST /{{tenant_id}}/manifests — DG Manifest
1{
2    "store_id": "your_store",
3    "manifest_group": "Parcel POST",
4    "contains_dangerous_goods": true
5}

Dangerous Goods Declaration Document

Where a carrier generates a DGD document, Rendr automatically retrieves and stores it. The signed document URL is available in the Create Delivery and Get Delivery responses under dangerous_goods_form_url.

To retrieve the DGD PDF directly:

GET {{domain}}/{{tenant_id}}/deliveries/{{delivery_id_or_reference}}/label/dgd