intelligent.pageDocs

Tata CLiQ

Tata CLiQ publishes no seller API: onboarding is a curated seller panel, and every working integration runs through Unicommerce, EasyEcom or Vinculum.

Tata CLiQ is the Tata Group's own marketplace, run by Tata Unistore Limited under Tata Digital, selling fashion, footwear, accessories, electronics, beauty and a separate luxury storefront. For a seller it is a curated marketplace: brands are onboarded by a category team, not by self service sign up, and the same curation applies to integration. There is no developer portal, no published endpoint reference and no self serve credential console. What does exist is a seller panel and a set of aggregator connectors that already hold working credentials. This page records what can be established from primary and aggregator sources, and is explicit about where the record stops.

At a glance

What it is

Tata CLiQ launched in 2016 as Tata Group's horizontal e-commerce play, operated by Tata Unistore Limited and now sitting inside Tata Digital alongside BigBasket, Tata 1mg and the Tata Neu super app. It is a marketplace, not a pure retailer: third party sellers list and hold their own stock, though Tata also runs first party and brand owned inventory on the same storefront. Distinct selling surfaces exist and are usually treated as separate channels by connectors: the main tatacliq.com marketplace, Tata CLiQ Luxury on luxury.tatacliq.com, and the beauty assortment. A notable Tata CLiQ mechanic is phygital or store fulfilment, where an order is routed to a physical brand store rather than a warehouse. That matters for the unified model because a single seller account can carry many fulfilment locations.

API access

There is no application you can start from a web page. The route sellers describe is:

  1. Get onboarded as a Tata CLiQ seller through a category manager, which produces seller panel credentials.
  2. Ask the Tata CLiQ integration or account team to enable API access for your seller code.
  3. Hand the credentials to an aggregator, or to your own connector if Tata CLiQ permits a direct integration for your account.

No API version, deprecation calendar, changelog or official SDK in any language could be found. www.tatacliq.com serves a single page application that returns HTTP 200 for every path including paths that do not exist, so a 200 on /sell-online or /sellerportal is not evidence that a seller documentation page lives there. Treat any such link with suspicion until it renders real content in a browser.

Warning

Public GitHub repositories exist that declare a Tata CLiQ connector with a base URL of https://sellerapi.tatacliq.com/v1 and a sellerId plus apiKey credential pair. That host does not resolve in DNS. Those repositories are generated scaffolding, not evidence. Do not build against them.

Authentication

Not published. No source we could read names a token endpoint, a header, a signature scheme or a token lifetime. Because the aggregator connectors are configured once and then run unattended for months, the mechanism is more likely a long lived key or a username and password that mints a session than an OAuth authorization code flow, but that is an inference from operational behaviour and nothing more. No code block is given here because there is no verified request to show.

Multi account handling is presumed to follow a seller code per selling entity, with a mapping from Tata CLiQ fulfilment location codes to your own warehouse codes, which is the pattern every Indian marketplace connector uses. Unverified.

Objects we can read

No endpoint can be documented. What can be documented is the object coverage the aggregator route gives you, which is the only route we can currently evidence.

Unicommerce lists Tata CLiQ among its marketplace integrations. Unicommerce's partner integration documentation states the set of APIs a marketplace must expose before Unicommerce will integrate it, which sets a floor on what Tata CLiQ's seller API supports:

  • authentication, by GET or POST
  • product count and live product listing retrieval
  • order retrieval
  • inventory update, described as posting revised inventory back to the marketplace
  • order status retrieval

Conditionally, where the operating model needs it: courier and shipment detail, shipping label retrieval, order acceptance and on hold handling, dispatch and cancellation notification, and invoice detail retrieval where the marketplace owns tax documents. Tata CLiQ issues invoices and ships on most of its assortment, so the shipping label and invoice endpoints are very likely present, but we have not seen them named.

Settlements are not in that floor set. Treat Tata CLiQ payment and commission reconciliation as a seller panel report download until proven otherwise.

Writing back: listings, price and stock

Stock and price updates are supported through the aggregator connectors, which is the same inventory update capability the Unicommerce floor set requires. Listing creation and catalogue enrichment on Tata CLiQ are panel driven: sellers upload category specific templates and the category team approves them. There is no published bulk feed format, no feed processing report format and no documented job status endpoint.

Practical position for a connector: plan on writing stock and price through an aggregator, and plan on listing creation being a manual panel workflow you can at best pre stage a spreadsheet for.

Webhooks and notifications

None published. Poll. A ten to fifteen minute order poll and an hourly inventory reconciliation is the cadence aggregators run on Indian marketplaces of this size, and is a safe starting point until Tata CLiQ gives you a rate limit in writing.

Rate limits and pagination

Not published. No quota headers, no burst or sustained numbers, no per app versus per seller split. Ask for them in writing during onboarding and record the answer, because there is nowhere to look them up.

Mapping to the unified model

Field names on the Tata CLiQ side are unknown, so this table records where each unified object has to come from rather than a field to field mapping.

Gaps and open questions

  • Whether a direct seller API is available to sellers at all, or only to approved integration partners, is unverified. Both models are common in India.
  • The authentication mechanism is entirely unverified.
  • Whether Tata CLiQ Luxury is a separate channel requiring its own credentials is unverified.
  • Whether settlement or payment reports are available through any API is unverified.
  • EasyEcom's knowledge base at support.easyecom.io sits behind a login wall and returned an HTTP 302 to a login page on 2026-09-21, so EasyEcom's Tata CLiQ article could not be read. Unicommerce's public integration list was readable and is the stronger source here.

Sources