Parent API: e-Way Bill API Quickstart guide Authentication guide

Update Transporter on e-Way Bill

Q: What parameters and payload format are required for Update Transporter?

Requests are submitted via HTTP POST to '/ewaybillapi/v1.03/ewayapi/updatetransporter'. Required parameters: 'email' (query parameter), 'ip_address' (header parameter), 'client_id' (header parameter), 'client_secret' (header parameter), 'username' (header parameter), 'gstin' (header parameter). A JSON request body ('Content-Type: application/json') is accepted per the schema specifications shown in the request documentation.

Q: What response status codes and format does Update Transporter return?

For Update Transporter (POST '/ewaybillapi/v1.03/ewayapi/updatetransporter'), responses are returned in JSON format ('application/json'). Documented response codes in the specification include: HTTP 404 (Not Found. If requested entity is not found or if requested API is not found.), HTTP 500 (Internal server error).

POSThttps://apisandbox.whitebooks.in/ewaybillapi/v1.03/ewayapi/updatetransporter

Update Transporter

e-Way Bill UI

Explore Feature

Generate & Manage e-Way Bills with Part-B Updates

Update vehicle numbers, extend validity in transit, and manage consolidated trip sheets without logging into the NIC portal.

Parameters

query parameters

emailstringrequired

User Email

irpstringoptional

e-WayBill Server Type(NIC1/NIC2)

header parameters

ip_addressstringrequired

IP Address

client_idstringrequired

Client ID

client_secretstringrequired

Client Secret

usernamestringrequired

User Name

gstinstringrequired

GSTIN number

Request Body

application/json

ewbNonumberoptional

EwayBill Number

Example: 381009282489

transporterIdstringoptional

15 Digit Transporter GSTIN/TRANSIN

Example: "05AAACG0904A1ZL"

Response

Not Found. If requested entity is not found or if requested API is not found.

Frequently Asked Questions

Requests are submitted via HTTP POST to /ewaybillapi/v1.03/ewayapi/updatetransporter. Required parameters: email (query parameter), ip_address (header parameter), client_id (header parameter), client_secret (header parameter), username (header parameter), gstin (header parameter). A JSON request body (Content-Type: application/json) is accepted per the schema specifications shown in the request documentation.

For Update Transporter (POST /ewaybillapi/v1.03/ewayapi/updatetransporter), responses are returned in JSON format (application/json). Documented response codes in the specification include: HTTP 404 (Not Found. If requested entity is not found or if requested API is not found.), HTTP 500 (Internal server error).

Update Transporter

Reject EwayBill

Extend Validity of E-Way Bill

POST/ewaybillapi/v1.03/ewayapi/updatetransporter

1const response = await fetch('https://apisandbox.whitebooks.in/ewaybillapi/v1.03/ewayapi/updatetransporter?email=value&irp=value', {

2 method: 'POST',

3 headers: {

4 ip_address: "value",

5 client_id: "value",

6 client_secret: "value",

7 username: "value",

8 gstin: "value",

9 Content-Type: "application/json"

10},

11 body: JSON.stringify({

12 "ewbNo": 381009282489,

13 "transporterId": "05AAACG0904A1ZL"

14}),

15});

17const data = await response.json();

18console.log(data);

No example available.