Shopclues

ShopClues is an Indian horizontal marketplace run by Clues Network Private Limited, founded in 2011 and acquired by Singapore's Qoo10 in 2019. It was once one of India's four largest marketplaces, built on unbranded and value goods sold by a long tail of small merchants from tier two and tier three towns. It is still online, and it still has a merchant panel and a live API host, but the developer documentation that its own footer links to has been broken for long enough that nobody has noticed. This page is unusually specific about what is and is not reachable, because in ShopClues' case the reachability is the story.

At a glance

What it is

ShopClues is a managed marketplace: merchants register themselves, list their own goods, and either ship themselves or use Fulfilment by ShopClues. The assortment skews to value priced unbranded goods across mobiles and accessories, home and kitchen, appliances, fashion, footwear, automotive and daily needs. The site still carries its consumer loyalty currencies, CluesBucks and CluesBucks Plus, and a VIP Club.

Several signals suggest the platform is maintained rather than actively developed. The homepage still embeds a Reliance General "Coronavirus Insurance" purchase widget with a policyholder declaration form. Product review dates visible in the page shell date to 2020. api.shopclues.com runs Apache 2.4.6 on CentOS with PHP 7.2.34 behind Varnish 4, a stack that passed end of life years ago. The copyright line reads "Copyright © 2011-2026 Clues Network Pvt. Ltd.", so the site is being kept current in at least that one respect.

API access

ShopClues calls it the "Shopclues open API". That name comes from the HTML title of the error page its own developer host serves, which is the only trace of the documentation left.

What you can verify today:

1. ShopClues' footer, on every page including https://www.shopclues.com/learn-to-sell.html, contains a link labelled "Developer Resources" pointing at http://developer.shopclues.com.
2. Over HTTPS, developer.shopclues.com serves the stock "Apache HTTP Server Test Page powered by CentOS" default page. The virtual host is not configured for TLS.
3. Over HTTP, the same host returns HTTP 500 with the page title "Internal error - Shopclues open API" and the body text "Cannot contact the database server: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) (localhost)". That is a wiki or CMS whose database is down, not a portal that was deliberately retired.
4. The Internet Archive holds no capture of developer.shopclues.com or api.shopclues.com, so the documentation cannot be recovered from the archive either.

There is therefore no route to read the API reference and no documented route to request a key. The practical answer is to raise it through merchant support at https://www.shopclues.com/merchant-support.html and expect the panel, not the API.

Authentication

API key based, and nothing beyond that is published.

The one thing that can be stated from observation: a GET to http://api.shopclues.com/ returns HTTP 301 to http://api.shopclues.com/api/version.ini, and that path returns HTTP 200 with the body:

{"result":[{"status":"failed","msg":"Invalid Key","error":"105"}]}

That tells you three real things and no more. Responses are JSON wrapped in a result array. Failures carry status, msg and a numeric error code, with 105 meaning an invalid or absent key. Authentication is a key, not an OAuth flow, because an OAuth protected endpoint would not phrase its rejection that way.

It does not tell you the parameter or header the key goes in, the token lifetime, whether keys are per merchant or per application, or what any other error code means. Do not guess.

Objects we can read

No endpoint can be documented, because the reference is unreachable. What exists on the merchant side, per ShopClues' own merchant pages, is the ordinary marketplace set: catalogue, orders, fulfilment, returns, commission and payments. All of it is reached through Store Manager.

Store Manager is the merchant panel, at http://storemanager.shopclues.com/vendor.php?dispatch=authorize.login_form. The vendor.php?dispatch=authorize.login_form URL shape is the CS-Cart Multi-Vendor convention, which makes it very likely ShopClues' merchant side is a CS-Cart Multi-Vendor deployment or a fork of one. That is an inference from a URL pattern, a strong one, but an inference. If it holds, the object model and the bulk import and export formats will follow CS-Cart's, which is worth checking before designing a file based integration.

Merchant registration, quoted from ShopClues' "How to Sell" page, is fully self serve:

1. Log in to Store Manager and click Register, entering an email address and phone number.
2. Enter the OTP sent to the phone.
3. Create a password.
4. Choose a store name.
5. Enter a pin code.
6. Enter a GSTIN.

Each merchant also gets a public storefront on a subdomain of the form <store-name>.shopclues.com. Public subdomain datasets contain thousands of these, which is a convenient way to enumerate the merchant base for market research without touching the API.

Fulfilment by ShopClues exists as a separate programme with its own policy page at https://www.shopclues.com/fulfillment-by-shopclues.html. If you use it, orders.fulfilment_type is platform and inventory.location_id points at a ShopClues warehouse you do not control.

Writing back: listings, price and stock

Through Store Manager. ShopClues' merchant guidance describes catalogue management as covering "Product Names, Images, Quantity, Specifications, Price and Description", and gives content rules: complete product names, key attributes, high resolution images with no text or artwork, clean backgrounds, detailed descriptions, no keyword spamming. Its pricing guidance asks merchants to compare prices across channels and to state clearly whether cash on delivery is available.

Whether the open API supports catalogue or inventory writes is unknown. Plan on the panel and its bulk upload until ShopClues gives you a specification.

Webhooks and notifications

None published. If you get API access, poll. Without API access, the panel and its exports are the only channel, and the practical cadence is whatever a human or a robotic process automation script can sustain.

Rate limits and pagination

Not published. The api.shopclues.com edge sits behind Varnish, so some caching and some throttling exist at the edge, but no quota header was observed and none is documented.

Mapping to the unified model

Platform field names are unknown. This records provenance rather than a field mapping.

Gaps and open questions

• The entire API reference is unrecoverable. Neither the live host nor the Internet Archive yields it.
• Whether the open API is still issued to new merchants at all, or whether it is a legacy surface kept alive for a handful of integrations, is unverified. The state of the developer host argues for legacy.
• Whether api-qa2.shopclues.com and apidebug.shopclues.com are a sandbox is unverified. They appear only in third party subdomain enumeration datasets, never in ShopClues documentation.
• The CS-Cart Multi-Vendor inference is from a URL pattern alone and should be confirmed before any file format decision rests on it.
• ShopClues does not appear on Unicommerce's current public integration list, which does name several smaller Indian marketplaces. Whether that means the integration was retired or simply is not marketed is unverified.

Sources

• ShopClues how to sell, source of the registration steps, catalogue and pricing guidance, and the footer link to Developer Resources
• ShopClues merchant support
• Fulfilment by ShopClues
• http://storemanager.shopclues.com/vendor.php?dispatch=authorize.login_form, the merchant panel login, HTTP 200 on 2026-09-21
• http://developer.shopclues.com, HTTP 500, page title "Internal error - Shopclues open API", MySQL socket error, on 2026-09-21. Over HTTPS the same host serves the CentOS Apache test page
• http://api.shopclues.com/api/version.ini, HTTP 200 returning the JSON error quoted above, on 2026-09-21
• Internet Archive availability API, no snapshots for the developer or API hosts
• ShopClues on Wikipedia, for the Qoo10 acquisition and founding history
• Public subdomain enumeration datasets on GitHub, for the existence of api-qa2.shopclues.com and apidebug.shopclues.com