intelligent.pageDocs

Vaaree

Curated Indian home decor marketplace: no public seller API, brands join by enquiry and connect through an aggregator such as Unicommerce.

Vaaree is an Indian home and decor marketplace that curates products from exporters, manufacturers and premium brands and sells them under one storefront at vaaree.com. From the shopper's side it reads like a single D2C brand. From the supply side it is a curated marketplace: Vaaree states it works with 350 or more exporters, manufacturers and premium brands, and runs a vetting process it describes as 32 or more category-specific checks including raw materials. There is no public developer portal and no published seller API. Partner onboarding is a manual enquiry, and the automated route for an existing brand is through an order management aggregator that already carries a Vaaree connector.

At a glance

What it is

Vaaree sells home decor and home essentials online in India: bedding, kitchen and dining, decor, storage and similar categories. Its positioning is curation rather than long-tail marketplace breadth, so the catalogue is narrower and more edited than a horizontal marketplace such as Amazon India or Flipkart. The storefront runs on Shopify, judging by the URL structure it serves (/pages/, /blogs/, /collections/), which matters because it caps what a seller-facing interface could look like: a Shopify store hosting multiple suppliers usually manages them through a multi-vendor app or through an internal ops tool, not through a bespoke seller API.

Unicommerce's published integrations catalogue lists Vaaree as a supported channel, describing it as "a home decor curated marketplace". That is the strongest evidence that a machine-readable seller connection exists at all, since an aggregator only builds and lists a connector when it has a working credential path.

API access

No public developer portal, no API reference, no SDK and no Postman collection was found. The footer of vaaree.com links only policies, about, contact, a partner page, an affiliate page, bulk gifting, a blog and order tracking. There is no /developers, no /api and no seller login.

The documented route to become a supplier is manual:

  1. Send a supplier or brand partnership enquiry through the contact page at vaaree.com/pages/contact.
  2. Include company name, product catalogue, categories, materials and a business contact person.
  3. Vaaree runs its category-specific quality checks before onboarding.

Commission, payment terms, fulfilment model (whether Vaaree buys inventory outright, holds it on consignment, or drop-ships from the supplier) and the existence of any seller dashboard are all unpublished. The partner page is a marketing page with a contact form, not a programme specification.

Note

Because the fulfilment model is unpublished, do not assume Vaaree orders are seller-fulfilled. If Vaaree purchases stock, the relationship is a purchase order flow and belongs in a procurement table, not in orders. Establish this in the onboarding conversation before designing the load.

The aggregator route

If a Vaaree connection is needed and no direct API is offered, the practical path is the same one Indian brands use for niche channels: route it through an order management platform that already lists Vaaree. Unicommerce is the confirmed one. The aggregator holds whatever credential Vaaree issues (most commonly seller-panel credentials or a per-seller API key that is not documented publicly), and your systems talk to the aggregator's API rather than to Vaaree. That adds a hop but it is the only route with a published existence proof.

Authentication

Not published. No token endpoint, header name, scope or credential type is claimed here because none was found in any primary source.

Objects we can read

Nothing is readable through a documented Vaaree interface. Through an aggregator connector the usual set is available, but the field names belong to the aggregator, not to Vaaree, so they are not reproduced here as if they were Vaaree's. Expect, at minimum, sale orders and their items, and a catalogue or listing sync.

No sample response can be published. Vaaree has not published a schema, and inventing one would be worse than the gap.

Writing back: listings, price and stock

Not documented. Two plausible mechanisms exist and neither is confirmed:

  • Catalogue submission by spreadsheet during onboarding, with Vaaree's team creating the products, which is the norm for curated marketplaces of this size.
  • Listing and inventory sync through the Unicommerce connector, if that connector supports writes for this channel.

Ask Vaaree directly which one applies, and specifically whether price is controlled by the supplier or set by Vaaree. For a curated marketplace that buys or consigns stock, price control usually sits with Vaaree, which would make listings.price unwritable by the brand.

Webhooks and notifications

None published. If the connection ends up being aggregator-mediated, use the aggregator's notification mechanism. If it ends up being panel-only, poll the panel export on whatever cadence Vaaree's operations team supports, and treat order acknowledgement service levels as the constraint rather than any technical limit.

Rate limits and pagination

Not published.

Mapping to the unified model

Provisional, pending confirmation of the actual interface.

Gaps and open questions

  • The direct seller interface, if any, is entirely unpublished. Everything above is bounded by what the public storefront and partner page say.
  • The /pages/sell-on-vaaree path returned HTTP 404; the live partner page is /pages/partner-with-vaaree. Older references to a "sell on Vaaree" page are stale.
  • Whether the Unicommerce connector is API based or panel based for this channel could not be verified. Unicommerce's own quick-commerce connectors are email based, so connector existence does not imply an API.
  • Commission, payment cycle and returns liability are unknown.
  • Web search was unavailable for this page, so findings rest on direct fetches only.

Sources