e-Way Bill APIs for Logistics — Generate, Extend, Cancel, and Update Part-B at Truck-Fleet Scale
Up to 1,000 e-Way Bills per single API call. p95 312 ms. 99.994% uptime during peak month-end dispatch.
Run a 30-day bulk EWB pilot — sandbox in 5 minutes
The problem
For Head of Logistics / IT at a transporter, 3PL, FMCG distributor. You generate 50,000+ e-Way Bills per month across 500+ vehicles. Manual portal entry breaks at scale. Vehicle changes mid-route force Part-B updates around the clock. During financial year-end, the NIC portal slows down exactly when your dispatch dock is at peak load.
How WhiteBooks solves it
- Bulk e-Way Bill generation: up to 1,000 EWBs in a single API call with idempotency keys — safe to retry without duplicate generation.
- Mid-route Part-B updates exposed as a single PUT call — no more swivel-chair between your TMS and the NIC portal.
- Consolidated EWB for multi-consignment trucks: one vehicle, many invoices, single document.
- Webhook fan-out (ewb.partb.updated, ewb.expired, ewb.cancelled) so your dispatch dashboard reacts in real time.
Key APIs
| Tool / Endpoint | What it does | Path |
|---|---|---|
eway.generate_bulk | 1,000 EWBs per call | /api/v1/bulk-generate |
eway.update_partb | Mid-route vehicle / transporter swap | /api/v1/update-part-b |
eway.consolidated_generate | Multi-consignment truck | /api/v1/consolidated |
eway.extend_validity | Truck delay beyond validity | /api/v1/extend |
eway.cancel | Within 24h NIC cancellation window | /api/v1/cancel |
Compliance angle
NIC compliance, Part-A vs Part-B clarity, 24-hour cancellation window, 100 km/day validity rules, transporter-id / GSTIN dual-mode addressing.
Live numbers
- Throughput: 1,000 invoices / EWBs per single API call (bulk mode).
- Latency: p50 87 ms IRN, p95 312 ms — live at whitebooks.in/status.
- Uptime: 99.994% rolling 30-day; 99.99% SLA with credits on Enterprise.
- Region: Mumbai + Hyderabad active-active; KSA in
me-south-1.
Sample architecture
Sample customer pattern
A national 3PL on WhiteBooks generates 1.6 M EWBs in a 24-hour peak during financial year-end. Their dispatch dock runs from a 12-line CSV import — every line becomes a bulk-generate call, results round-trip in under 4 seconds for 1,000 EWBs.
Frequently asked questions
Can WhiteBooks handle our peak month-end dispatch volume?
Yes. Production traffic exceeds 9 crore IRNs + EWBs annually with peak bursts above 1.6 M EWBs in a 24-hour window. Bulk generation accepts up to 1,000 EWBs per call and the API is idempotent so retries do not double-generate.
How does Part-B (vehicle) update work for mid-route changes?
Call PUT /api/v1/update-part-b with the EWB number, new vehicle number, transporter document number, and from-place. The endpoint is webhook-instrumented so your TMS can react to the partb.updated event in real time.
What happens when a truck breaks down and the EWB is about to expire?
Use eway.extend_validity with a reason code (typically "natural calamity" or "trans-shipment"). NIC allows extension up to 24 hours before expiry; WhiteBooks proxies the call directly to NIC with no manual portal access required.
Do you support consolidated e-Way Bills for multi-consignment trucks?
Yes. eway.consolidated_generate accepts a vehicle number plus an array of EWB numbers. Returned consolidated number replaces the individual EWBs for inspection. Required when a single vehicle carries multiple invoices.
What is the NIC cancellation window and can we cancel via API?
24 hours from EWB generation, provided the EWB has not been verified at a check-post. eway.cancel takes the EWB number, a NIC reason code, and remarks; the cancellation is final and reported back via webhook.
Get started
Related use cases: Logistics · Retail · Manufacturing · Fintech · Pharma · E-Commerce · SaaS · CA Firms · ERP Providers
Reference: All APIs hub · /docs/gst · /docs/einvoice · /docs/eway · Pricing · Architecture · Status · Changelog