intelligent.pageDocs

Limeroad

Limeroad, owned by V-Mart Retail, publishes no seller API and no public seller page: the only evidenced route is an aggregator such as Unicommerce.

Limeroad is an Indian fashion marketplace for women's, men's and kids' apparel, footwear and accessories, best known for its Scrapbook feature, a user generated look builder. It was acquired by the listed value retailer V-Mart Retail in 2023 and now runs as part of that group. For a seller it is a curated fashion marketplace. There is no developer portal, no seller documentation, and as of 2026-09-21 no "sell with us" page anywhere on the public site. What does exist is a working aggregator integration: Unicommerce names Limeroad on its public marketplace integration list. That is the whole of the verifiable record, and this page says so plainly.

At a glance

What it is

Limeroad launched in 2012 as a social discovery and shopping site: users assembled outfit "scrapbooks" from catalogue items, and those scrapbooks drove discovery. The commerce underneath is a marketplace across women's clothing, men's clothing, kids, footwear, accessories and home decor, at value price points. V-Mart Retail's ownership shows through in the product: the live site carries a /vmart/exclusive section and a vmart.limeroad.com hostname appears in certificate transparency records, so the two businesses share assortment and infrastructure.

The seller base skews to small and mid sized fashion suppliers rather than large brands, which is the same population that sells on Meesho and Snapdeal, and which in practice reaches every one of those channels through a single aggregator rather than through direct integrations.

API access

Not documented, and not applied for from a web page.

What was checked on 2026-09-21:

  • seller.limeroad.com, vendor.limeroad.com and developer.limeroad.com do not resolve.
  • api.limeroad.com resolves and answers, but it serves the consumer storefront HTML behind an AWS load balancer, not a seller API. It is the app's own front end host.
  • /sell, /seller, /sell_on_limeroad, /sellonlimeroad, /sell-with-us and /vendors on www.limeroad.com all return HTTP 404. Unlike several other sites in this catalogue, Limeroad does return real 404s, so those are genuine absences rather than a single page application catch all.
  • The homepage footer contains no seller, vendor or partner link at all. The outbound link set is entirely consumer facing.
  • A certificate transparency search over limeroad.com returns about thirty hostnames. None is a seller, vendor, partner or developer host. Ones that hint at the back office are neft.limeroad.com, which by its name relates to bank transfers and so plausibly to vendor payouts, omni.limeroad.com and pay.limeroad.com. None is documented and none should be probed.

The one positive signal is external: Unicommerce's public integration list names Limeroad among its supported marketplace and e-commerce channels. Unicommerce's partner integration documentation states the API set a marketplace must expose before Unicommerce will integrate it, so Limeroad's appearance on that list implies, at minimum, an authentication call, product count and product listing retrieval, order retrieval, inventory update and order status retrieval.

Warning

The absence of any public seller page is unusual and worth treating as a live risk rather than a documentation gap. A marketplace that has removed its seller acquisition funnel may have narrowed onboarding to invitation only, or may be consolidating into its parent's operations. Confirm the channel is open to new sellers before you scope work on it.

Authentication

Not published. No token endpoint, header, key name, lifetime or scope model is documented by any source we could read. No code block is given because there is no verified request to show. Assume, until told otherwise, a credential set issued by Limeroad per seller entity, in line with every comparable Indian marketplace, and assume you will hold one credential set per selling entity with a mapping table from Limeroad location codes to your warehouses.

Objects we can read

No endpoint can be documented. Object coverage through the aggregator route, inferred from Unicommerce's stated minimum for any marketplace integration:

  • Orders. Retrievable, with status. This is the mandatory set.
  • Order items. Implied by orders.
  • Products and listings. Retrievable, including a product count call and a live listing call.
  • Inventory. Write direction only in the Unicommerce model: you post revised stock to the marketplace.
  • Shipments and tracking. Conditional in Unicommerce's model, present where the marketplace arranges carriage and exposes labels. Limeroad ships most of its orders, so labels and courier detail are likely present.
  • Returns and cancellations. Conditional. Cancellation notification is in the conditional set.
  • Payments and settlements. Not in the required set. Treat as a panel report download.
  • Customers. Indian fashion marketplaces mask buyer contact details. Assume masked until proven otherwise.
  • Locations. Present as opaque Limeroad location codes.

Writing back: listings, price and stock

Stock and price through the aggregator inventory sync. Listing creation on a curated fashion marketplace is a catalogue template upload plus category approval, not an API call you can rely on. There is no published bulk feed format and no published processing report format.

Webhooks and notifications

None published. Poll. For a fashion marketplace of this size a ten to fifteen minute order poll and an hourly stock reconciliation is a sensible starting cadence, to be revised the moment Limeroad gives you a written rate limit.

Rate limits and pagination

Not published.

Mapping to the unified model

Platform field names are unknown, so this records provenance.

Gaps and open questions

  • Whether Limeroad is still onboarding new third party sellers is unverified, and the removal of the seller funnel from the public site is a reason to ask before you build.
  • Whether a direct API is available to sellers, or only to approved aggregators, is unverified.
  • Whether V-Mart ownership has moved Limeroad onto V-Mart's vendor systems, which would change the integration entirely, is unverified. The shared vmart.limeroad.com host shows the businesses are technically joined, it does not show how.
  • The authentication model is entirely unverified.
  • EasyEcom's knowledge base at support.easyecom.io is login walled, returning an HTTP 302 to a login page on 2026-09-21, so EasyEcom's Limeroad article could not be read.

Sources