Skip to main content
POST
Reject E-Way Bill

NIC validations

  1. E-way bill can be rejected by the other party involved in the e-waybill, if generated by the supplier/recipient.
  2. E-way bill can be rejected by supplier or recipient, if it is generated by the transporter.
  3. E-way bill can be rejected within 72 hours of generation of e-way bill

Request body schema

View request body schema

Authorizations

authorization
string
header
required

E-Way Bill taxpayer access token returned by Authenticate.

x-api-key
string
header
required

Sandbox API key from your Sandbox account.

Headers

x-api-version
string
default:1.0.0

API version

x-source
enum<string>
default:primary

NIC server for the session used by this request. primary selects NIC1. secondary selects NIC2. Defaults to primary. See NIC1 and NIC2 routing.

Available options:
primary,
secondary
x-proxy
enum<string>

NIC server that receives the request. If omitted, the request goes to the server selected by x-source. When specified, selects the other server. See NIC1 and NIC2 routing.

Available options:
primary,
secondary

Path Parameters

ewb_no
string
required

Response

200 - application/json

200 EWB rejected / 344 Invalid EWB number / 341 Generator cannot reject EWB

An E-Way Bill success or NIC business-failure response. Both variants use HTTP 200.

code
enum<integer>
required

NIC response code.

Available options:
200
timestamp
integer<int64>
required

Unix timestamp.

transaction_id
string
required

Request transaction identifier.

data
object
required