intelligent.pageDocs

Shipdelight

ShipDelight is an Indian 4PL with a private client API (token, AWB generation, tracking) released only to onboarded brands; no public developer portal.

ShipDelight is an Indian e-commerce logistics platform and 4PL operator aimed at D2C lifestyle brands. It sits between a brand's storefront and a panel of courier partners, choosing a carrier per shipment, generating waybills and labels, running the tracking page and the NDR and RTO workflows, and reporting on delivery performance by pincode and payment mode. For a connector the interesting objects are shipments, tracking event history, NDR and RTO state, and COD remittance, not listings. There is no public developer portal: API credentials and documentation are handed to onboarded clients by the ShipDelight team, so most of what follows is established from aggregator integration guides rather than from first-party reference docs.

At a glance

What it is

ShipDelight is a Mumbai-headquartered logistics technology company that positions itself as an "eCommerce logistics platform and 4PL for lifestyle brands". Its own site claims 300 or more brands on the platform, next-day delivery in 30 or more cities, over 100 million deliveries of experience across the founding team, and a 10 percent reduction in RTO for clients. The company states it received a LEAPS award from the Government of India for innovation in logistics. Named brand references on the site include Mokobara.

The commercial model is aggregator-style: the brand ships through ShipDelight, ShipDelight allocates across underlying courier partners, and the brand sees one dashboard, one tracking page and one reconciliation. The product emphasis is post-purchase, that is NDR management, RTO reduction, branded tracking and returns, rather than pure rate arbitrage.

This matters to a seller connector because ShipDelight is the system of record for a shipment's carrier, AWB, status history and delivery outcome once an order leaves the warehouse, even though the underlying carrier may be Delhivery, Ecom Express, Blue Dart, India Post or another partner.

API access

There is no public developer portal and no self-serve API key issuance.

  • The marketing site's integrations section names Shopify, BigCommerce, Unicommerce and Razorpay among supported systems, and states that ShipDelight "integrates with your websites, marketplaces, WMS, CRM, ERPs, couriers, communication channels, payment gateways and BI tools". It gives no developer links. The only calls to action are "Book a Demo" and contacting sales.
  • https://shipdelight.com/developers/ and https://shipdelight.com/integration/ both return HTTP 404 as of 2026-09-21.
  • Host probing on 2026-09-21 found: docs.shipdelight.com and developer.shipdelight.com do not resolve; app.shipdelight.com and app-dev.shipdelight.com serve the same client application shell titled "SD-V3"; track.shipdelight.com serves the consumer order-tracking page; api.shipdelight.com returns HTTP 200 with a page titled "ShipDelight" containing only an "Employee login" form with an "Upload Certificate" field. That last host is an internal staff login, not an API reference.
  • No official SDK exists. A GitHub repository search for "shipdelight" on 2026-09-21 returned six repositories, all personal accounts with zero stars; the three that look like ShipDelight internal projects (pracheesd/ShipDelight-3.0-Tracking-Services, sandeep1384/ShipDelight-3.0-Client-Services, kunales2197/Shipdelight-Client-Services) are empty or contain only a README. There is no published Postman collection.
Warning

A document titled "InstaLogix ShipDelight Prod API Documentation 1.2" is indexed on Scribd, and its search-result description names a Token Generation API for access tokens, a Tracking API keyed on airway bill numbers, and an AWB Generation API. The document itself sits behind a bot challenge and could not be read. Treat the three API names as a weak signal about the shape of the surface, and treat any endpoint path, header or field you find quoted from it elsewhere as unverified until ShipDelight confirms it in writing.

Authentication

Not published in any first-party source. What can be stated:

  1. ShipDelight issues a User Name and Password to the client. The Unicommerce integration form lists both as mandatory and says each is "Provided by ShipDelight Team".
  2. Those credentials are exchanged for an access token. This is inferred from the "Token Generation API for generating access tokens" phrase in the client API document description, and is the standard pattern across Indian aggregators. The token endpoint path, the request body field names, the response field that carries the token, the header used to present it, and the token lifetime are all not published.
  3. Multi-account handling is not documented. Since credentials are per client, a credential store should key on channel_account_id equal to the ShipDelight client account, with one username, password and cached token per account.

No token request or authenticated call sample is given here, because writing one would mean inventing endpoint paths and field names. Ask ShipDelight for the current client API document before implementing.

Objects we can read

Shipments and tracking

This is the only object surface with any public evidence.

  • A Tracking API keyed on the airway bill number is named in the client API document description. Endpoint, parameters and response schema are not published.
  • The Unicommerce guide confirms that "AWB Tracking is provided in Uniware for Shipdelight shipped orders", meaning ShipDelight returns status updates that an external system can persist against an AWB.
  • Forward and reverse shipments are both supported. Forward shipments may be COD or prepaid; reverse pickups are prepaid only.
  • The label is a ShipDelight-generated PDF. The Unicommerce form has a Fetch Label Link flag which the guide says should be set to false so that ShipDelight's own label format is used, implying the API can either return a label document directly or return a URL to one.
  • A manifest is also produced by ShipDelight.

Sample responses are not published. The event vocabulary, the NDR reason codes and the RTO status names are not published.

Orders, order items, products, listings, inventory, customers, locations

Not applicable in the read direction. ShipDelight does not hold a catalogue. Orders enter ShipDelight as shipment creation requests from the brand's store or OMS. Consignee name, address and phone travel with the shipment request and are therefore PII held by ShipDelight, but there is no documented customer read endpoint.

Locations exist as a pickup address book: the Unicommerce form has a Pickup Address Id field that the seller configures "per ShipDelight instructions", so pickup locations are pre-registered by ShipDelight and referenced by an opaque id rather than created through the API.

Payments and settlements

COD remittance is part of the commercial relationship and appears in the client dashboard. No settlement API is published.

Writing back: listings, price and stock

Not applicable, this is a carrier. ShipDelight has no product catalogue, no price and no sellable stock, so there is nothing to write back in the listings sense.

The write path is shipment lifecycle:

  • Create shipment and generate AWB. Named as the "AWB Generation API" in the client document description. The Unicommerce form carries a Hand Over Mode option with values Drop or Pick, which selects between the brand dropping at a hub and ShipDelight arranging a pickup, and a Service Type field whose permitted values are not published. Request and response schemas are not published.
  • Pickup request. Implied by the Pick hand-over mode rather than documented as a separate call. Shipway's marketing page for its own ShipDelight integration lists "Automatic Pickup request generation" as a feature, which suggests pickup is either implicit in shipment creation or a separate call available to integrators.
  • Cancel shipment. Not documented in any source read. The Unicommerce guide explicitly does not cover cancellation. Assume it exists, confirm before building.
  • Label and manifest retrieval. Label PDF and manifest are produced by ShipDelight, per the Unicommerce guide.

There is no documented bulk or feed mechanism.

Webhooks and notifications

No client-facing webhook subscription mechanism is published. ShipDelight clearly ingests carrier events internally, since it runs a branded tracking page and an NDR product, but nothing states that a brand can register a callback URL for status pushes.

Until confirmed otherwise, plan to poll:

  • Poll tracking by AWB for every shipment that is not in a terminal state (delivered, rto_delivered, lost).
  • A 30 to 60 minute cadence is the usual fit for Indian last-mile carriers, where scans arrive in batches a few times a day. Do not poll more often than every 15 minutes without an agreed rate limit, since none is published.
  • Stop polling an AWB 7 days after it reaches a terminal state, to keep the working set bounded.

Ask ShipDelight directly whether a status push or a daily event file is available; aggregators of this size usually offer one to larger clients even when it is absent from the standard document.

Rate limits and pagination

Not published. No rate-limit headers, quota numbers, burst allowance or pagination model could be found in any source. Assume a conservative limit and implement client-side throttling with exponential backoff until ShipDelight states a number in writing.

Mapping to the unified model

Only shipments can be populated with any confidence. Field names on the platform side are unknown, so the right column records what the value is rather than a field name we cannot verify.

Gaps and open questions

  • No first-party API reference could be read. Every endpoint, header, field name, status value and limit is unverified.
  • Whether the "InstaLogix" prefix on the indexed client API document means ShipDelight's platform is built or white-labelled on a product called InstaLogix, or whether InstaLogix is a client, is unresolved. Worth asking, because it would tell us whether the API shape is shared with other carriers.
  • Whether webhooks exist for larger clients is unknown and is the single highest-value question to ask, since polling every open AWB is the expensive alternative.
  • Shipment cancellation, rate and serviceability checks by pincode, and COD remittance reporting are all undocumented. Serviceability in particular is normally exposed by aggregators of this type and is likely to exist.
  • app-dev.shipdelight.com may or may not be a usable sandbox for clients. It serves the client application, not an API reference, so it cannot be assumed to be one.

Sources

  • ShipDelight homepage, read 2026-09-21. Product positioning, integration names, no developer links.
  • ShipDelight, About Us, read 2026-09-21. Company claims, LEAPS award, scale figures.
  • https://api.shipdelight.com/, https://app.shipdelight.com/, https://app-dev.shipdelight.com/, https://track.shipdelight.com/, probed 2026-09-21. Host behaviour described above.
  • Unicommerce support, Integration with ShipDelight, read 2026-09-21. The only source with concrete configuration field names: User Name, Password, Hand Over Mode, Pickup Address Id, Fetch Label Link, Service Type, API URL.
  • Shipway blog, ShipDelight API integration, read 2026-09-21. Marketing only, no endpoints. Confirms forward and reverse support, thermal labels, automatic pickup request generation.
  • TrackingMore, ShipDelight tracking API, read 2026-09-21. Third-party aggregator page; confirms ShipDelight has its own tracking API but publishes none of its details.
  • Scribd document "InstaLogix ShipDelight Prod API Documentation 1.2", search-result metadata only, 2026-09-21. The document body is behind a bot challenge and was not read.
  • GitHub repository search for "shipdelight" via the GitHub API, 2026-09-21. Six repositories, none an official SDK, three empty.