E-Way Bill master data

This page lists the official NIC master codes used in Sandbox E-Way Bill API requests and responses. Match each code to its named field. A numeric code has no meaning outside its category.

​

Request field index

​

Request values

​

Supply and sub-supply types

Use supplyType and subSupplyType when you generate an E-Way Bill. When subSupplyType is 8 (Others), provide the reason in subSupplyDesc.

​

Document types

Use docType when you generate an E-Way Bill.

​

Transport modes

Use transMode for the transport mode in the relevant request.

​

Units

Use these unit codes in itemList[].qtyUnit when you generate an E-Way Bill and in unitCode for multi-vehicle movement.

​

Vehicle update and consolidated-bill reasons

Use reasonCode when you update vehicle details, regenerate a consolidated bill, or start multi-vehicle movement.

​

Vehicle number formats

Use one of these official templates for vehicleNo. Do not replace these templates with a custom regular expression.

​

Vehicle types

Use vehicleType when the request supports a vehicle type.

​

Cancellation reasons

Use cancelRsnCode when you cancel an E-Way Bill.

​

Validity-extension reasons and consignment status

Use extnRsnCode to explain a validity extension. The extension request also includes consignmentStatus.

​

Transaction types

Use transactionType when you generate an E-Way Bill.

​

Response and reference values

The following values appear in E-Way Bill responses or describe the generation channel. Do not send them as request inputs unless an endpoint explicitly documents them.

​

Mode of generation

genMode identifies the generation channel in an E-Way Bill response.

​

E-Way Bill status

The E-Way Bill payload uses these values in its status field.