intelligent.pageDocs

ShipLog

ShipLog, an Indian quick-commerce carrier known only through ClickPost; no first-party site or API documentation could be found.

ShipLog is listed by ClickPost as an integrated Indian carrier: "an Indian logistics and fulfillment company offering quick shipping solutions to direct-to-consumer (D2C) brands", specialising in "4-hour and same-day deliveries" with "dark store fulfillment, API-based integrations, and automated pick & pack operations". That one aggregator page is the only substantive source found. No first-party ShipLog website, developer portal or API reference could be located, and the obvious domains are occupied by three unrelated products that share the name. This page records what is verifiable and flags the identification problem rather than papering over it.

Warning

The name is ambiguous and the catalogue entry needs disambiguation before a connector is scoped. Four distinct things use the name ShipLog, and only one of them is an Indian carrier.

At a glance

What it is

Everything known comes from ClickPost's carrier integration page. ShipLog is described as Indian, operating only in India, serving direct to consumer brands with 4-hour and same-day delivery, running dark store fulfilment with automated pick and pack. ClickPost lists its services as "Shiplog Reverse", "4-hour Delivery", "Pick & Pack", "Real-time Tracking" and "Plug & Play APIs".

That profile places ShipLog in the hyperlocal and quick commerce tier of Indian logistics, alongside Dunzo, Shadowfax's hyperlocal arm, Pidge, Porter and Zippee, rather than in the national parcel tier with Delhivery, Ecom Express and Xpressbees. Dark store fulfilment means the inventory sits in micro-warehouses close to the buyer and the carrier picks, packs and delivers, so ShipLog is closer to a fulfilment provider than a pure line-haul carrier. If that is right, a merchant using ShipLog would want inventory-at-dark-store data as well as shipment data, and neither is documented.

ClickPost assigns ShipLog partner ID 5, which in ClickPost's numbering is an early integration, suggesting the relationship predates most of the 400-plus carriers now on the platform.

The name collision

Four unrelated products carry the name, and none of the three that are reachable is the Indian carrier:

Other candidates checked and found not to exist or not to be relevant: shiplog.co.in, shiplogindia.com, shiplogindia.in, shiplog.tech, shiplog.global, shiplog.shop, shiplog.us, getshiplog.com (a "Coming Soon" holding page), shiplog.ai (a personal site belonging to an unrelated founder in San Francisco), shiplogistics.in (a Hyderabad packers and movers business).

Note

Recommendation for the catalogue: either record ShipLog as a ClickPost-only carrier with no direct integration path and a partner ID of 5, or retire the entry until a first-party identity is confirmed. Do not attempt to scope a direct connector from the current evidence, and do not let anyone integrate against shiplog.co or shiplog.io by mistake. They are different products with different owners.

API access

Not obtainable directly, because no first-party contact point could be found. There is no website, no sales page, no support address and no developer portal for the Indian ShipLog in any source read.

The one workable route is through ClickPost, which is pre-integrated. That route is fully documented and public, which makes it the practical recommendation:

  • ClickPost's developer documentation is at docs.clickpost.ai, with a complete machine-readable index at docs.clickpost.ai/llms.txt and a markdown version of any page available by appending .md to its URL.
  • Access is an enterprise contract with ClickPost. Credentials come from an onboarding manager, not self-serve.
  • Carriers are addressed by a cp_id carrier partner ID in every order creation, tracking registration and order detail call. ShipLog's is 5.
  • ClickPost states it is pre-integrated with more than 300 couriers and that a new carrier can be enabled in a single click once contracted.

Going through ClickPost means you write one integration and get ShipLog plus every other Indian carrier the merchant uses, with a normalised status vocabulary and a single NDR bucket taxonomy. The cost is a second commercial relationship and a second margin. For a carrier with no reachable first-party interface, that trade is clearly worth it.

Authentication

Not published for ShipLog directly.

Through ClickPost there are two documented schemes. Either pass an enterprise username and key with the request, or exchange credentials for a short-lived token:

curl --location 'https://www.clickpost.in/api/v1/user/token/' \
  --header 'Content-Type: application/json' \
  --data '{ "username": "test_username", "password": "some_strong_password" }'

{ "token": "1123123123123123106", "expires_at": "2025-03-28T11:12:07" }

The token is valid for 24 hours and is then passed in the headers of subsequent API requests. expires_at is UTC. ClickPost's documentation says to obtain the username and password from an onboarding manager or from ClickPost support. Refresh on a schedule rather than on failure, since a 24 hour token will expire mid-sync at some point.

Objects we can read

Nothing can be read directly, because no direct interface is documented. What ClickPost's integration table claims ShipLog supports, with the caveat that this is ClickPost describing its own integration rather than ShipLog describing its API:

ClickPost names six ShipLog APIs: a Manifestation and Label Generation API to "Automate creating labels and orders in Shiplog's network", a Track Shipment API to "Fetch real-time tracking updates from the carrier's network", a Cancellation API, an EDD API for delivery timelines on the product page, an NDR Action Update, and Return Webhooks to "Trigger and initiate return orders quickly".

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

None. ShipLog is a carrier and a fulfilment provider, not a sales channel. Note that a dark-store fulfilment model implies inventory held at ShipLog locations, which would be genuinely useful if exposed, but nothing suggests it is.

Shipments and tracking

Through ClickPost, the shipment lifecycle is covered by documented endpoints: order creation for India, AWB registration for tracking, tracking by polling, tracking by webhook, a fetch-updated-shipment-list endpoint that returns every AWB updated in a time window, and serviceability by pin code. ClickPost also publishes an NDR bucket code taxonomy that normalises each carrier's free-text non-delivery remarks into standard buckets, which is exactly what you want when the carrier's own vocabulary is undocumented.

Returns and cancellations

ClickPost documents reverse order creation with quality check, and lists Return Webhooks among ShipLog's capabilities, plus a "Shiplog Reverse" service. Reverse logistics is therefore supported, but the object shape is ClickPost's, not ShipLog's.

Proof of delivery

ClickPost's table marks POD as supported and ClickPost publishes a Fetch Proof of Delivery endpoint that "takes the waybill/AWB as input and returns the proof of delivery in PDF format as an URL". Whether the underlying ShipLog POD is a signature, a photo or an OTP is not stated anywhere.

Payments and settlements

Nothing. No COD remittance, rate card or invoice surface is described in any source.

Locations

Dark stores are central to the described model, but no serviceability list, dark store list or coverage map was found. ClickPost's bulk serviceability endpoint would return serviceable pin codes per carrier partner, which is the only practical way to discover ShipLog's coverage.

Writing back: listings, price and stock

Not applicable, this is a carrier. ShipLog holds no listing, price or stock that a buyer sees, so there is nothing to write.

The write path is shipment creation and cancellation, and through ClickPost it is documented: create a single-piece or multi-piece order for India against cp_id 5, fetch the AWB and the shipping label, place a pickup request, cancel the shipment, and push an NDR action back to the carrier. ClickPost's NDR Action Update is described as updating "the after NDR action directly on the courier company's database", which means the action reaches ShipLog rather than stopping at ClickPost.

No direct ShipLog write path is documented anywhere.

Webhooks and notifications

Not published for ShipLog directly.

Through ClickPost: configure a webhook URL on the ClickPost dashboard and ClickPost posts tracking status updates to it. ClickPost documents an All Status Webhook, a separate endpoint for additional tracking details, and a best practices page for consuming status updates. That is the route to push for ShipLog shipments.

If you end up polling instead, ClickPost's fetch-updated-shipment-list endpoint takes a start and end time and returns every AWB updated in that window, which is far cheaper than polling per AWB. For a 4-hour delivery carrier the useful polling interval is short, 15 minutes or less, because the entire shipment lifecycle can complete inside one hour.

Rate limits and pagination

Not published for ShipLog. Not read for ClickPost either; consult ClickPost's integration guidelines page before sizing a sync.

Mapping to the unified model

Only shipments is in scope, and only through ClickPost. Field names below are ClickPost's concepts, not ShipLog's, and the mapping should be built once for ClickPost and reused for every carrier behind it.

orders, order_items, listings, inventory, settlements, customers and locations are all out of scope for this platform.

Gaps and open questions

  • The carrier cannot be identified as a standalone live product. No website, no company page, no contact address, no press coverage reachable by the fetcher. The entire evidence base is one aggregator marketing page. It is possible ShipLog has been renamed, acquired or wound down since ClickPost integrated it, and the page simply survives.
  • The name collides with three other live products, two of which are software tools with no connection to shipping in India. This is the highest-risk part of the entry: someone will integrate the wrong ShipLog.
  • ClickPost's carrier pages are partly templated. The benefit claims on the page ("Reduce RTO rates by 57%", "Improve sales by 20%") are generic ClickPost marketing repeated across carriers, not ShipLog-specific facts. Only the integration capability table and the descriptive paragraph should be treated as carrying information, and even those are ClickPost's account of its own integration.
  • Dark store inventory. If ShipLog really holds merchant inventory in dark stores, there should be a stock-at-location surface. Nothing describes one.
  • Coverage. Which cities ShipLog serves, and at what service level, is unknown. ClickPost's bulk serviceability endpoint is the way to find out, but it needs a live ClickPost account.
  • No rate, COD or settlement surface described anywhere.

Sources