The cargo manifest
When the destination discharges a declaration, ITS produces the declaration's cargo manifest. The destination's customs system loads it to take the goods in. Every DISCHARGED declaration has exactly one, including a transit ITS closed because the destination is not on ITS.
The manifest follows the ASYCUDA AWMDS manifest layout, element for element. You read it with the declaration's own serial number:
| Read | Request | Permission |
|---|---|---|
| The declaration | GET /api/v1/etd/{serial_no} | etd:read |
| Its manifest | GET /api/v1/manifest/{serial_no} | manifest:read |
You can read the manifest of every declaration you can read. Anything else answers 404, exactly like a serial that was never issued (see Reading and searching).
To know whether a manifest exists yet, and which formats it can be read in, read the declaration with ?include=manifest (see Is there a manifest yet?). Before discharge the manifest read answers 409 BUS-ETD-134; the include is simply absent.
Choose a format
format | Media type | What you get |
|---|---|---|
json (the default) | application/json | The manifest under data, in the usual response envelope. |
asycuda-awmds | application/xml | The <Awmds> document, ready to load. |
| A code the Secretariat publishes | as published | The same manifest in a layout the Secretariat has added for systems that load a different one. |
curl -H "Authorization: Bearer $TOKEN" \
"$ITS_GATEWAY/api/v1/manifest/UGKLATD2026102400000123?format=asycuda-awmds&tz=Africa/Kampala"
A manifest never changes once it is produced. Keep the ETag and send it back as If-None-Match: ITS answers 304 and sends nothing again.
What ITS fills, and what it leaves to you
ITS fills an element only from a value the declaration holds. Every other element is written empty in the XML and null in JSON, for your system to complete as your procedures require. ITS never invents an identifier and never assumes a code.
| AWMDS element | Filled from |
|---|---|
Customs_office_code, Place_of_destination_code, Place_of_unloading_code | Box 2, the office of destination, as country and office code (UG and KLA give UGKLA) |
Place_of_departure_code, Place_of_loading_code | Box 1, the office of departure |
Date_of_departure | The release stamp of the departure country: when the goods left, not when the declaration was lodged |
Date_of_arrival, Time_of_arrival | The discharge stamp. Empty when ITS closed the transit itself |
Total_number_of_bols, Line_number | Always 1: one declaration is one consignment |
Total_number_of_packages, Number_of_packages | Box 7 |
Total_gross_mass, Gross_mass | Box 9, in kilograms |
Total_number_of_containers, Num_of_ctn_for_this_bol | 1 when box 8 is filled, otherwise 0 |
ctn_segment (Ctn_reference, Number_of_packages) | Box 8 and box 7; present only when box 8 is filled |
Carrier_name, Carrier_address | Box 5, when it is filled |
Mode_of_transport_code, Nationality_of_transporter_code | The means of transport that arrived: the last one a stamp recorded; otherwise boxes 17 and 18; otherwise boxes 15 and 16 |
Exporter_name, Exporter_address | Box 3 |
Consignee_name, Consignee_address | Box 4 |
Package_type_code | Box 28, when every commodity line declares the same kind |
Goods_description | Box 25 of every commodity line, in line order, separated by ; |
Always empty, for you to complete: Voyage_number, Master_information, Carrier_code, Bol_reference, Bol_nature, Bol_type_code, Unique_carrier_reference, Notify_name, Notify_address, Shipping_marks, Volume_in_cubic_meters, Type_of_container, Empty_Full, PC_indicator, Location_code, Location_info.
ITS keeps every stamp time in UTC and writes the manifest in UTC unless you send tz. Send your own zone, for example tz=Africa/Kampala, so that an arrival near midnight carries your date. ITS never guesses a zone from a country, because some countries span more than one.
When ITS closed the transit because the destination is not on ITS, Date_of_arrival and Time_of_arrival are empty: that closure is not evidence that the goods arrived. See Discharge: closing the transit.
The AWMDS document
A consignment in a container, discharged at Kampala:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Awmds>
<General_segment>
<General_segment_id>
<Customs_office_code>UGKLA</Customs_office_code>
<Voyage_number></Voyage_number>
<Date_of_departure>2026-10-20</Date_of_departure>
<Date_of_arrival>2026-10-24</Date_of_arrival>
<Time_of_arrival>14:35:12</Time_of_arrival>
</General_segment_id>
<Totals_segment>
<Total_number_of_bols>1</Total_number_of_bols>
<Total_number_of_packages>525.0</Total_number_of_packages>
<Total_number_of_containers>1</Total_number_of_containers>
<Total_gross_mass>25100.0</Total_gross_mass>
</Totals_segment>
<Transport_information>
<Carrier>
<Carrier_code></Carrier_code>
<Carrier_name>EAST AFRICA HAULIERS LTD</Carrier_name>
<Carrier_address>P.O. BOX 1234, MOMBASA</Carrier_address>
</Carrier>
<Mode_of_transport_code>3</Mode_of_transport_code>
<Nationality_of_transporter_code>KE</Nationality_of_transporter_code>
<Master_information></Master_information>
</Transport_information>
<Load_unload_place>
<Place_of_departure_code>KEMBA</Place_of_departure_code>
<Place_of_destination_code>UGKLA</Place_of_destination_code>
</Load_unload_place>
</General_segment>
<Bol_segment>
<Bol_id>
<Bol_reference></Bol_reference>
<Line_number>1</Line_number>
<Bol_nature></Bol_nature>
<Bol_type_code></Bol_type_code>
<Unique_carrier_reference></Unique_carrier_reference>
</Bol_id>
<Load_unload_place>
<Place_of_loading_code>KEMBA</Place_of_loading_code>
<Place_of_unloading_code>UGKLA</Place_of_unloading_code>
</Load_unload_place>
<Traders_segment>
<Exporter>
<Exporter_name>SUNRISE MACHINERY EXPORTS</Exporter_name>
<Exporter_address>PLOT 7, INDUSTRIAL AREA, MUNDRA</Exporter_address>
</Exporter>
<Notify>
<Notify_name></Notify_name>
<Notify_address></Notify_address>
</Notify>
<Consignee>
<Consignee_name>KAMPALA SUGAR WORKS LTD</Consignee_name>
<Consignee_address>PLOT 12, JINJA ROAD, KAMPALA</Consignee_address>
</Consignee>
</Traders_segment>
<ctn_segment>
<Ctn_reference>MRSU5228406</Ctn_reference>
<Number_of_packages>525</Number_of_packages>
<Type_of_container></Type_of_container>
<Empty_Full></Empty_Full>
</ctn_segment>
<Goods_segment>
<Number_of_packages>525</Number_of_packages>
<Package_type_code>NE</Package_type_code>
<Gross_mass>25100.0</Gross_mass>
<Shipping_marks></Shipping_marks>
<Goods_description>SUGAR PLANT MACHINERY SPARES; ELECTRICAL CONDUCTORS</Goods_description>
<Volume_in_cubic_meters></Volume_in_cubic_meters>
<Num_of_ctn_for_this_bol>1</Num_of_ctn_for_this_bol>
</Goods_segment>
<Value_segment>
<Freight_segment>
<PC_indicator></PC_indicator>
</Freight_segment>
</Value_segment>
<Location>
<Location_code></Location_code>
<Location_info></Location_info>
</Location>
</Bol_segment>
</Awmds>
Without a container (box 8 empty), Total_number_of_containers and Num_of_ctn_for_this_bol are 0 and there is no ctn_segment.
The JSON manifest
The same fields, and no others. Each AWMDS segment is an object named after it in lower case, each element a property in lower case, and bol_segment and ctn_segment are arrays. An empty element is null, so every property is always present.
{
"data": {
"general_segment": {
"general_segment_id": {
"customs_office_code": "UGKLA",
"voyage_number": null,
"date_of_departure": "2026-10-20",
"date_of_arrival": "2026-10-24",
"time_of_arrival": "14:35:12"
},
"totals_segment": {
"total_number_of_bols": 1,
"total_number_of_packages": 525.0,
"total_number_of_containers": 1,
"total_gross_mass": 25100.0
},
"transport_information": {
"carrier": {
"carrier_code": null,
"carrier_name": "EAST AFRICA HAULIERS LTD",
"carrier_address": "P.O. BOX 1234, MOMBASA"
},
"mode_of_transport_code": "3",
"nationality_of_transporter_code": "KE",
"master_information": null
},
"load_unload_place": {
"place_of_departure_code": "KEMBA",
"place_of_destination_code": "UGKLA"
}
},
"bol_segment": [
{
"bol_id": {
"bol_reference": null,
"line_number": 1,
"bol_nature": null,
"bol_type_code": null,
"unique_carrier_reference": null
},
"load_unload_place": {
"place_of_loading_code": "KEMBA",
"place_of_unloading_code": "UGKLA"
},
"traders_segment": {
"exporter": { "exporter_name": "SUNRISE MACHINERY EXPORTS", "exporter_address": "PLOT 7, INDUSTRIAL AREA, MUNDRA" },
"notify": { "notify_name": null, "notify_address": null },
"consignee": { "consignee_name": "KAMPALA SUGAR WORKS LTD", "consignee_address": "PLOT 12, JINJA ROAD, KAMPALA" }
},
"ctn_segment": [
{ "ctn_reference": "MRSU5228406", "number_of_packages": 525, "type_of_container": null, "empty_full": null }
],
"goods_segment": {
"number_of_packages": 525,
"package_type_code": "NE",
"gross_mass": 25100.0,
"shipping_marks": null,
"goods_description": "SUGAR PLANT MACHINERY SPARES; ELECTRICAL CONDUCTORS",
"volume_in_cubic_meters": null,
"num_of_ctn_for_this_bol": 1
},
"value_segment": { "freight_segment": { "pc_indicator": null } },
"location": { "location_code": null, "location_info": null }
}
]
}
}
Errors
| Code | HTTP | When | What to do |
|---|---|---|---|
VAL-ETD-138 | 400 | format is not one ITS serves, or it is no longer active. | Use json, asycuda-awmds or a published code. |
VAL-ETD-034 | 400 | tz is not an IANA zone. | Send a zone such as Africa/Kampala. |
RES-ETD-001 | 404 | No such declaration, or you may not read it. | Check the serial number. |
BUS-ETD-134 | 409 | The declaration is not yet discharged. | Read it again after the discharge. |