Install Waaru through the Shiprocket App Store flow.
Provider permission and endpoint acceptance, seller installation, webhook-secret setup, and sandbox testing remain required before production use.
Look up an order, shipment, AWB, non-delivery item, or courier option while the customer is asking. A reattempt or return-to-origin remains an explicit operator-controlled write.
In one line
Waaru reads bounded Shiprocket order, shipment, tracking, NDR, and serviceability data. It can explicitly request one NDR reattempt or return-to-origin and receive tracking updates.
Capability review updated .
Maintained by the Waaru product team. Read our editorial and product-claim review method.
No credit card. No commitment.
The workflow can read the NDR state, but a reattempt or return-to-origin requires an explicit write with a recorded idempotency key.
Shipment SR-2841
Customer details are omitted
Operating boundary
The seller installs Waaru through Shiprocket's managed App Store flow.
Read bounded order, shipment, AWB tracking, NDR, courier serviceability, and rate data.
Explicitly request one NDR reattempt or return-to-origin. Each action uses an idempotency key.
Verified tracking updates can continue the relevant customer journey.
Install the app, configure the generated webhook endpoint and one-time secret, then test in the sandbox.
No order fulfilment, shipment or AWB creation, pickup, manifest, label, invoice, or buyer-data mutation.
Each NDR write makes one provider attempt. Uncertain outcomes remain visible for reconciliation instead of being repeated blindly.
Order and shipment
Fetch one order, find an exact source-channel order, list up to twenty recent orders, or read one shipment summary. Safe outputs omit buyer name, email, phone, address, and seller credentials.
Tracking and serviceability
Read bounded AWB tracking activity or check courier serviceability and rates for the permitted route fields. A verified tracking update can continue the relevant customer journey.
Delivery exceptions
Fetch one non-delivery item or list up to twenty recent items. The connector exposes two writes: request another delivery attempt or request return-to-origin for one shipment. Each makes one provider attempt and preserves an uncertain outcome for reconciliation.
Webhook setup
The seller configures Waaru's generated HTTPS endpoint and security token in Shiprocket. Tracking events are accepted only after an exact secret match and durable deduplication.
Current boundary
The connector does not create, update, cancel, clone, import, or fulfil orders. It does not create shipments, AWBs, pickups, manifests, labels, invoices, or international shipments, and it does not alter addresses, dimensions, courier assignment, or buyer data.
Yes. A workflow can retrieve bounded tracking activity for one AWB and use verified tracking updates as events.
Research notes
Primary Shiprocket references for managed installation and provider operations.
Shiprocket documents its App Store installation and seller-token exchange flow.
Shiprocket App Store API documentation · Accessed 13 August 2026
Shiprocket publishes API references for order, shipment, tracking, courier, and NDR operations.
Shiprocket API documentation · Accessed 13 August 2026
Ready to ship a WhatsApp flow that doesn't break?
Apply for founding access. No credit card. Cancel anytime.