Pikndel

Pikndel is an Indian quick-commerce logistics startup offering ecommerce brands a shared dark store plus a delivery fleet: stock sits in Pikndel fulfilment centres, and orders go out on 1-hour, same-day or next-day promises. For a connector the objects that matter are serviceability, order creation with AWB and label, pickup, tracking events, proof of delivery and NDR. There is no public developer portal and no published endpoint reference. Pikndel's own site confirms an API exists ("Connect through Shopify, WooCommerce, or Magento connectors, upload CSV, or utilise API") but credentials and documentation are issued per client. This page records what can be established from Pikndel's site, the Unicommerce integration guide and ClickPost's carrier page.

At a glance

What it is

Pikndel is a venture-backed Indian logistics technology company. Its model is a shared dark store: rather than each brand building its own micro-fulfilment network, brands place stock in Pikndel's fulfilment centres and Pikndel delivers, with options ranging from 1-hour to same-day to next-day. It describes itself as a quick commerce partner and positions on post-purchase experience, running its own courier fleet and handling "where is my order" enquiries on the brand's behalf.

Funding and recognition, from its own site as of 2026-09-21: a $285,000 pre-seed round led by 100X.VC, a $1 million seed round led by VC Grid and others, and an ICC Excellence Award for Domestic Courier and Express. ClickPost describes it as "a B2B logistics tech startup that provides shared dark stores and fulfillment services for e-commerce brands".

Two facts matter for a connector. First, it is small and recent, so expect the API to be thin and the documentation to be a PDF from an account manager. Second, Unicommerce records that only forward shipments are supported and that Pikndel is a last-mile courier partner, so returns and reverse pickups may not exist on the API at all even though the company runs warehouses.

API access

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

• Host probing on 2026-09-21: pikndel.com serves the marketing site; docs.pikndel.com, developer.pikndel.com, app.pikndel.com and track.pikndel.com do not resolve; api.pikndel.com returns HTTP 200 with the stock "Welcome to OpenResty!" page, and returns 404 for /docs, /swagger, /api-docs, /openapi.json, /v1, /api/v1 and /health. An API gateway is clearly there; nothing about it is published.
• Pikndel's own site lists the integration options as Shopify, WooCommerce and Magento connectors, CSV upload, or the API, with no developer link.
• Onboarding is described on the site as contract signing, then account setup, then dispatch. That is a sales process, not a developer signup.
• No official SDK, Postman collection or OpenAPI document exists. A GitHub search on 2026-09-21 found only unrelated personal repositories.

Authentication

Not published. What is known comes from the Unicommerce connector form:

Note two differences from the identical-looking forms for ShipDelight and Shippigo: Pikndel's Pickup Address Id and API Url are both blank by default, which suggests a single fixed base URL and no pre-registered pickup address book. And the recommended hand-over mode is Drop, meaning the brand drops at a Pikndel dark store rather than Pikndel collecting.

No token request or authenticated call sample is given here, because writing one would mean inventing endpoint paths and field names.

Objects we can read

Shipments and tracking

The only object with public evidence.

• Unicommerce confirms "AWB tracking is present" and that "AWB will be fetched from Pikndel", meaning the waybill is minted by a Pikndel API call rather than from a pre-allocated series.
• The label PDF is produced by Pikndel. The manifest is produced by Uniware, not by Pikndel, which is a meaningful difference from ShipDelight and Shippigo where the carrier supplies the manifest.
• ClickPost's carrier matrix for Pikndel marks order creation, cancellation, tracking by polling, tracking by webhook, proof of delivery, non-delivery report and create pickup request as supported, with the label generated by ClickPost rather than by the carrier. ClickPost lists no partner id for Pikndel and gives the country as India.

Endpoint paths, request and response schemas, the tracking event vocabulary, NDR reason codes and delivery status names are all not published.

Inventory and products

Not published, and this is the notable gap. Pikndel operates shared dark stores holding brand-owned stock, so an inventory position exists inside their system. No inventory, SKU or stock API is documented anywhere, and Unicommerce integrates Pikndel purely as a shipping provider rather than as a warehouse. If dark-store stock visibility matters, that is the first thing to ask about.

Orders, listings, customers, locations, settlements

Not applicable in the read direction, this is a carrier. Orders enter as shipment creation requests. Consignee name, address and phone travel with the request and are therefore PII held by Pikndel. No pickup-address-book endpoint is implied, since the Unicommerce Pickup Address Id field is blank by default. No settlement or COD remittance API is published, though COD is supported as a shipping method.

Writing back: listings, price and stock

Not applicable, this is a carrier. Pikndel holds no product catalogue, channel price or sellable listing, so there is nothing to write back in the listings sense.

The write path is the shipment lifecycle. What can be asserted:

• Create order and fetch AWB. Confirmed indirectly: Unicommerce configures forward COD and prepaid shipping methods with "AWB Generation selected as API", and states the AWB is fetched from Pikndel.
• Label. Returned by Pikndel as a PDF, per Unicommerce. Fetch Label Link set to False means the label document rather than a URL.
• Pickup request. Marked supported by ClickPost. The Unicommerce hand-over mode defaults to Drop, so pickup is available but not the recommended flow for that route.
• Cancel. Marked supported by ClickPost. Not documented anywhere first-party.
• NDR action. Marked supported by ClickPost. No first-party reference.
• Reverse shipments. Unicommerce states explicitly that only forward shipments are supported. Confirm before promising returns.

No bulk or feed mechanism is published.

Webhooks and notifications

Pikndel publishes nothing. ClickPost marks tracking by webhook as supported, but that describes an integration ClickPost has built, not a subscription endpoint a client can call.

Until Pikndel confirms otherwise, plan to poll:

• Poll tracking by AWB for every shipment not in a terminal state.
• For a quick-commerce operator the whole lifecycle is hours, not days, so the useful cadence is much tighter than for a national courier: every 5 to 15 minutes while a shipment is open, then stop entirely once delivered. A 1-hour delivery promise polled hourly is worthless.
• Because shipments resolve within a day, the open set stays small, which makes polling cheap here in a way it is not for Delhivery or Ecom Express.

Ask Pikndel directly whether a status callback is available. For a company this size the answer is often yes, on request, even when nothing is documented.

Rate limits and pagination

Not published. No limits, quota headers, burst allowance or pagination model could be found. Throttle client-side and use exponential backoff until Pikndel states a number in writing.

Mapping to the unified model

Only shipments can be populated, and the platform-side field names are unknown, so the right column records what the value is rather than a field name that cannot be verified.

Gaps and open questions

• No first-party API reference could be read. Every endpoint, header, field name, status value and limit is unverified.
• Is there a dark-store inventory API? This is the highest-value question. Pikndel holds brand stock; if that position is readable, Pikndel can populate inventory and locations, not just shipments.
• Whether reverse shipments are supported at all. Unicommerce says no; ClickPost's matrix does not address it.
• Whether the label comes from Pikndel or must be generated by the caller. The two aggregator sources disagree.
• Whether a status callback is available, and at what granularity. For 1-hour delivery, webhook latency matters more than it does for a national courier.
• How the 1-hour, same-day and next-day commercial promises map onto the Service Type values the API accepts.
• Whether serviceability is a per-pincode check or a published list. Unicommerce models it as a pincode list defined in Uniware, which suggests Pikndel may not expose a serviceability endpoint at all.
• No COD remittance reporting is documented.

Sources

• Pikndel homepage, read 2026-09-21 through a rendering proxy. Shared dark-store model, 1-hour, same-day and next-day promises, integration options (Shopify, WooCommerce, Magento, CSV, API), funding and award claims, onboarding process.
• Unicommerce support, Integration with Pikndel, read 2026-09-21. The only source naming concrete configuration fields: User Name, Password, Service Type, Hand Over Mode, Pickup Address Id, Fetch Label Link, API Url. States forward shipments only, last-mile courier partner, label PDF from Pikndel, AWB fetched from Pikndel, AWB tracking present, manifest from Uniware.
• ClickPost, Pikndel carrier integration, read 2026-09-21. Capability matrix marking order creation, cancellation, polling, webhook, POD, NDR and pickup request as supported, with ClickPost-generated labels; describes Pikndel as a B2B shared dark-store and fulfilment startup.
• Host probing of api.pikndel.com, docs.pikndel.com, developer.pikndel.com, app.pikndel.com and track.pikndel.com, 2026-09-21.
• GitHub repository and code search for "pikndel", 2026-09-21. No official SDK or documentation.