Get E-way bill for Transporter by Date#
Available only in sandbox.
Given a date, a transporter could fetch all E-way bills assigned to him on the date.
Route
/basic/einv/{flynn-version}/{irp}/{e-invoice-api-version}/ewayapi/GetEwayBillsForTransporter?date={Date}
- active ‘flynn-version’: v3.0
- method: GET
URL Parameters#
Name | Description | Type |
---|---|---|
flynn-version | version of the API for example, v3.0 |
string |
irp | IRP Provider as per GST registration for e-invoicing | enum (ni1, ni2) |
e-invoice-api-version | E-invoice API version | string |
QUERY Parameters#
Name | Description | Type |
---|---|---|
date | date (format DD/MM/YYYY, like 31/12/2020) | string |
Headers#
All headers as mentioned in the Basic E-Invoice API introduction.
Tip
The only valid value for the header key accept
is application/json
.
Also, since no request body is sent, header key Content-type
is optional.
Response#
200
:#
Successful response will be the same payload as per the ‘E-Invoice API Documentation’ published by NIC.
Sample Response Body
{
"status": "1",
"data": [
{
"ewbNo": 611009906019,
"ewbDate": "21/06/2021 11:37:00 AM",
"status": "ACT",
"genGstin": "24AAAPI3182M002",
"docNo": "1624255223737",
"docDate": "21/06/2021",
"delPinCode": 110025,
"delStateCode": 7,
"delPlace": "Delhi",
"validUpto": "02/07/2021 11:59:00 PM",
"extendedTimes": 0,
"rejectStatus": false
}
],
"error": null,
"info": null,
"additionalInfo": null,
"alert": null
}
502
:#
If any Error from NIC end then sample response will be as per below.
Sample Response Body
{
"status": "0",
"data": null,
"error": {
"message": "err-irp-returned-error",
"type": "Irp",
"args": {
"details": [
{
"ErrorCode": "336",
"ErrorMessage": null
}
]
}
},
"info": null,
"additionalInfo": null,
"alert": null
}
E-invoice errors are mentioned under common errors for v3.0 api.
Notes#
IRP - nic is deprecated. Instead of it please use ni1 or ni2