India's value marketplace as JSON: price, MRP, the shop behind the listing and per-size stock

Seven actions. search runs a keyword search and returns up to 100 products in one call. product/detail opens one product by its short code or its URL for the full record: price, the MRP Meesho publishes, the offer breakdown, size variants with their own price and stock, the reseller shop, the rating breakdown, images, the attribute table, the breadcrumb, the delivery estimate and the return options. product/reviews returns the star breakdown and the review rows. category/browse reads a Meesho category page. categories, search/filters and search/suggest are free: the browsable taxonomy three levels deep, the filters and sorts Meesho offers for one query, and its own search-box completions. Prices are INR and no Meesho account is used.

Where Meesho publishes them, and it often does not. Across 600 search rows in twelve categories a struck price was present on 16 percent, from 4 percent on kids toys and bluetooth earbuds to 48 percent on face wash. Where there is none, original_price and discount_percent come back null rather than as a number worked out from something else. The product record publishes the MRP and the discount against it when Meesho prints them there, and a category listing prints the struck price somewhat more often than search does.

search returns up to 100 rows in a single request, and that is the cheap way to get depth because a 100-row page costs the same as a 20-row one. Page with the cursor the response hands back: page two fetched that way shared 0 of 20 rows with page one, while a bare page number on its own re-serves page one, so a page number is walked internally instead, one upstream call per page and no deeper than page ten. A category page is different: Meesho renders about twenty products on it, so limit there trims that page rather than fetching more.

Only the ones Meesho publishes for that exact query, which search/filters returns free: colour, price band, rating, discount, fabric, size, category and gender among them, with every value each accepts. A value Meesho does not know is refused here with the real values named, because Meesho answers an unknown filter by returning the unfiltered set, which looks like a filter that worked. Two things to know: the 2.0, 3.0 and 3.5 and above rating bands return the same set as each other, so they are Meesho's own bands rather than three thresholds, and a price band is a label rather than an exact range. Sorting is relevance or newest. There is no price sort on Meesho web search, so price_asc is refused rather than accepted and answered with nothing.

Meesho pads an empty search with unrelated products rather than saying zero, and publishes no total to contradict it: a nonsense query returned twenty products led by a kids jigsaw puzzle. Every keyword search is judged against its own query tokens, and a page where fewer than a quarter of the rows answer the query comes back as NOT_FOUND with fallback_results set. Pass include_fallback_results to get those rows anyway, still flagged.

Yes, as a shop rather than a brand. Meesho runs on resellers, so its own brand field on a listing is the supplier name. Rather than present a shop as a manufacturer, this API returns no brand field at all and gives you shop instead: name, handle, shop URL, its own rating, rating count, products listed and products sold, plus the manufacturer and Meesho Mall verification flags. These are business facts that Meesho publishes; no personal contact detail is read or constructed.

Per variant, yes, and the two kinds of blank are kept apart. variants carries each size with its own id, name, price and in_stock flag. in_stock is false only where Meesho states the size is out of stock, and null where Meesho lists the size but publishes no stock behind it. The product-level stock flag is deliberately not copied down onto sizes, because that would publish a sold-out size as available.

Whatever Meesho does not publish, and it says so. total_results is always null because Meesho publishes no total. Attributes arrived on 58 percent of 600 rows, everything on sarees and wall clocks and nothing at all on men's t-shirts and wrist watches, and a rating on 87 percent, dropping to 46 percent on bluetooth earbuds. Reviewer names are Meesho's own display names and are overwhelmingly the literal string Meesho User. product/reviews cannot tell a dead product code from a product with no reviews, because Meesho answers both with an empty summary, so the error says exactly that and points at product/detail, which can. The reviews cursor can still be set on the last page, so stop on an empty one. Delivery is the estimate Meesho prints on the page with its cash-on-delivery flag, not a promise for a given pincode, and there is no pincode parameter.

Meesho API is a ReefAPI endpoint group for india's value marketplace: mrp and selling price kept apart, the reseller shop behind each listing, per-size stock. It returns live JSON through POST requests under /meesho/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. Meesho calls use the same shared credit balance as every other ReefAPI engine.

No login to Meesho is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

Meesho actions currently cost 1-2 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call meesho actions with the same key, credit pool and JSON envelope used by normal REST requests.