Shipping API Integration for Indian Ecommerce: The Complete Technical Guide

Direct courier API integration means connecting individually to Delhivery's API, XpressBees' API, Ecom Express' API, etc. — each with its own authentication, endpoints, request/response format, error handling, and documentation quality. A full integration with 3 couriers takes 3–6 weeks of developer time and requires ongoing maintenance as each courier updates their API.

Aggregator API integration means connecting once to a platform like ApnaCourier that normalizes all courier APIs behind a single, consistent interface. One integration unlocks all connected couriers. The tradeoff: you lose access to courier-specific edge features, and you depend on the aggregator's uptime. For most Indian ecommerce businesses, aggregator API is the right choice — lower integration cost, faster time-to-market, and single maintenance burden.

Every shipping API, whether direct or aggregator, supports three core operations: (1) Create Shipment — POST request with order details (weight, dimensions, addresses, COD/prepaid, declared value) returns AWB number and label data; (2) Track Shipment — GET request with AWB number returns current status and movement history; (3) Cancel Shipment — DELETE/POST request before pickup cancels the shipment and avoids charges.

Additional operations available in most APIs: Rate Check (get shipping cost before committing to courier), Serviceability Check (is this pincode serviceable?), NDR Update (provide buyer response to failed delivery), Bulk AWB Generation, and Manifest Generation (end-of-day pickup manifest). Always implement serviceability check at checkout to avoid creating undeliverable orders.

Polling tracking status (checking every 15 minutes via GET request) is inefficient — it generates unnecessary API calls and introduces latency. Webhooks are the modern standard: the courier or aggregator pushes status updates to your endpoint when something changes. You receive tracking events — Picked Up, In Transit, Out for Delivery, Delivered, Undelivered — as HTTP POST requests to your configured webhook URL.

Webhook implementation: register your webhook URL in the courier/aggregator dashboard, set up an HTTP POST handler at that URL that receives the tracking event payload, authenticate the webhook (verify shared secret in request header), process the event (update order status, trigger customer notification, log for analytics), and return HTTP 200 within 30 seconds to acknowledge receipt. Use a queue (AWS SQS, Redis) between your webhook receiver and processing logic to handle traffic spikes.

Shipping labels come in two formats: PDF (standard, printable on any printer) and ZPL (Zebra Programming Language, for thermal label printers). For volume above 100 labels/day, thermal label printers (Zebra GK420d or TSC DA210 at ₹8,000–₹15,000) pay for themselves in time savings within a month. Below 100 labels/day, PDF printing on A4 paper cut to size is sufficient.

Bulk label generation via API: submit an array of order objects in a single POST request, receive an array of AWBs and a merged PDF or ZIP of individual label files. Most aggregator APIs support bulk label generation of 50–500 shipments per request. For very high volumes (2,000+ labels/day), use asynchronous bulk generation: submit the request, receive a job ID, poll for completion, then download the label file. This prevents API timeout on large batches.

Shopify integration options: (1) ApnaCourier Shopify app — one-click install, auto-syncs orders, generates labels from Shopify admin, pushes tracking back to order; (2) Custom API integration via Shopify's Order webhook + carrier service API — more flexibility but requires developer setup; (3) Shopify Shipping (Shopify's native solution) — limited to international carriers, not useful for Indian domestic shipping.

WooCommerce integration: ApnaCourier WooCommerce plugin auto-syncs orders, generates labels in bulk, and updates tracking numbers on WooCommerce orders. For custom WooCommerce setups with non-standard order flows, use the REST API: subscribe to WooCommerce order.created webhooks, call ApnaCourier API to create shipment, write back AWB and tracking URL to WooCommerce order meta. Total developer time for clean custom WooCommerce integration: 2–4 days.