API Features
API Features
(Dated: 18.07.2024)
2. At e-Invoice1 portal, you can access services of einvoice2 and vice versa. That is, IRNs
generated at e-Invoice2 Portal will be available at e-Invoice1 for cancellation and e-
waybill generation. Similarly, IRNs generated at e-Invoice1 will be available at e-
Invoice2.
3. To access the services of einvoice2, namely ‘Get IRN’, ‘Cancel IRN’ and ‘Eway bill by
IRN’ from einvoice1, the URL and end points are same as of einvoice1, an additional
header parameter ‘irp’ with value ‘NIC2’ needs to be passed, which indicates that
service requested is from e-Invoice2. Similarly ‘irp’ should be ‘NIC1’ to access these
services of e-Invoice1 from e-Invoice2.
In the absence of ‘irp’ header parameter, APIs will work for the data available locally
or the URL accessed.
1. For direct e-Waybill operations, e-Waybill1 and e-Waybill2 API systems are made
operational in sandbox environment. e-Waybill2 runs in parallel with e-Waybill1
System, but with the following critical functionalities.
Generate E-Way Bill
Update Vehicle Details
Update Transporter Details
Get E-Way Bill
Cancel E-Way Bill
3. At e-Waybill1 System, you can access the services namely ‘Get E-way bill’, ‘Part B
updation’ of e-Waybill2 System and vice versa. That is, e-Waybills generated at e-
Waybill2 System can be retrieved and part B can be updated from e-Waybill1 System.
Similarly, e-waybills of e-Waybill1 can be retrieved and part B can be updated from e-
Waybill 2. e-Waybill2 system synchronises the e-Waybill details with e-Waybill1
System within a few seconds.