Collect Meesho listings as clean JSON: value-segment prices in INR, discounts, seller names, ratings, sizes and delivery details from a single REST call. We handle proxies, rendering and parsing, so your team can compare supplier pricing, find fast-moving products and watch competitors.
# Request (replace the key and URL with your own)
POST https://api.webfusiondata.com/v1/product
Authorization: Bearer $WFD_API_KEY
{ "url": "https://www.meesho.com/example-cotton-kurta/p/EXAMPLE123",
"country": "IN" }
# Response (sample data, not a live listing)
{
"product_id": "EXAMPLE123",
"marketplace": "IN",
"title": "Example Cotton Kurta",
"brand": "Example Brand",
"price": { "amount": 399.00, "currency": "INR" },
"availability": "Available",
"rating": 4.5,
"product_url": "https://www.meesho.com/example-cotton-kurta/p/EXAMPLE123"
}Sample values for illustration only. Exact field names and nesting for your Meesho scope are confirmed in the API reference issued with your key.
A Meesho Product Data API reads Meesho listings for you and returns them as structured records. Send a product link or a keyword and receive JSON with title, category, price in INR, discount, sizes, rating, seller and availability. The schema is the same every time, so results load straight into price comparison tools, resale catalogues and BI reports.
Our side of the work covers managed proxies, page rendering, Meesho-specific parsing and field validation before any response goes out. Big batches run in the background and are delivered by webhook or to cloud storage, so your team only needs a simple HTTPS integration.
Resellers, sellers and market researchers use Meesho data to compare low-price listings, check how suppliers price similar products, follow fast-moving categories and benchmark delivery and ratings. Our price monitoring and price intelligence services build on the same data.
From choosing what to collect to loading it into your own systems, in six steps.
Pick what you need from meesho.com: one product page, a batch of product IDs turned into URLs, or a keyword or category search.
List the fields that matter most, such as INR price, discount, seller or delivery, so they can be checked against what the pages show.
Create a JSON body with url (or site and query) and an optional country.
Select /v1/product for one listing, /v1/search for result lists, /v1/monitor for scheduled tracking or /v1/bulk for batches.
Pass your API key as a bearer token in the Authorization header.
The sandbox lets you test with sample responses before any live request credits are used.
We open the Meesho page, render it, extract the fields and validate them. Single lookups answer in the same request.
Bulk jobs return a job ID that you check at /v1/status/:job_id or receive by webhook.
JSON is the default, and bulk exports can be delivered as CSV or XLSX.
Every record includes crawled_at, so you can see exactly when a price was captured.
Save results to a database, show them in a BI dashboard, trigger alerts from webhooks or run recurring checks with monitors.
See Integration and Data Delivery for a worked example.
What the Meesho Product Data API offers, and which parts are documented today versus settled per project.
Returns the core Meesho page record: title, category path, brand where shown, images and product attributes. Use it to map Meesho listings to your resale catalogue and to compare similar products across suppliers.
Meesho product links end in /p/ID, so a list of product IDs becomes a list of URLs for /v1/product. The ID is returned in each record for matching.
Captures the price in INR and, where shown, the original price and percentage off. Register a page for scheduled checks with a webhook on change to run a Meesho price monitoring API workflow for margin and resale pricing.
Returns the star rating and rating count on each listing, so you can sort suppliers by quality signals and watch how ratings change over time.
Returns the seller shown on the listing where displayed, which helps you compare suppliers selling similar products. Seller profile pages and other offers are confirmed per project.
Returns delivery charge or free-delivery labels and payment options such as cash on delivery, where the page shows them. Pincode-specific details are confirmed per project.
The country parameter sets the marketplace for each request. For Meesho that is the Indian site, meesho.com, and any other scope is confirmed at onboarding.
Fields are type-checked and normalised, and automated checks hold back malformed responses before delivery.
Use recurring monitors, webhook callbacks or bulk exports to cloud storage, so refreshed data reaches you without manual work.
The fields our Meesho product data extraction can return, what each means and how resale and pricing teams use it. Availability follows what each page displays.
| Data Field | Description | Business Application | Availability |
|---|---|---|---|
product_id | Meesho product ID from the product URL | Product identification, de-duplication | Core |
title | Product name as listed | Catalogue management, content checks | Core |
category / brand | Category path, and brand where one is shown | Category benchmarking, assortment mapping | Core |
price.amount / price.currency | Displayed price and its currency (INR) | Price comparison, resale margin inputs | Core |
discount | Original price and percentage off when shown | Discount depth analysis | Where displayed |
variants | Sizes and colours listed on the page | Size-run and assortment analysis | Where displayed |
rating / review_count | Star rating plus rating and review counts | Supplier and product quality comparison | Where displayed |
seller | Seller name shown on the listing | Supplier benchmarking | Where displayed |
availability | Displayed stock status | Out-of-stock alerts, availability monitoring | Core |
delivery / payment_options | Delivery charge or label and payment options such as cash on delivery | Landed-cost and conversion analysis | Confirm at onboarding |
reviews (text) | Individual review content | Sentiment and NLP pipelines | Confirm at onboarding |
product_url / crawled_at | Page URL and capture timestamp | Reference, freshness checks, time series | Core |
Core = part of the standard field set on our ecommerce API. Where displayed / available / exposed = returned when the listing on that marketplace shows it, so it can be empty for some products. Confirm at onboarding = settled per project. Images and specification tables are also returned. Field names are illustrative; your API reference is the source of truth.
The Meesho Product Data API uses the same versioned endpoints as the Ecommerce Scraping API. Meesho-specific parameter names that are not yet published are marked as illustrative.
| Endpoint | Purpose | Parameters | Expected response |
|---|---|---|---|
POST /v1/productDocumented |
One Meesho listing returned as structured data: INR price, seller, rating, variants and attributes. | Required: urlOptional: country; a dedicated product_id field is a confirm |
One JSON product record, returned synchronously. |
POST /v1/searchDocumented |
Keyword or category search on meesho.com, returned as a structured result list. | Required: site (e.g. "meesho"), queryOptional: country |
JSON with query, result_count and a results array. |
POST /v1/monitorDocumented |
Registers a listing for scheduled price and stock monitoring with webhook notifications. | Required: urlOptional: webhook URL and check frequency names: confirm |
A monitor ID you use to read tracked data later. |
GET /v1/monitor/:idDocumented |
Latest tracked data and change history for one monitored product. | Required: id (path) |
JSON with the current values and recorded changes. |
POST /v1/bulkDocumented |
Submits a batch of URLs for asynchronous processing; results go to storage or a webhook. | Required: list of URLs Optional: delivery destination and format (JSON, CSV or XLSX) names: confirm |
A job ID, then results via webhook or storage export. |
GET /v1/status/:job_idDocumented |
Status and progress of an asynchronous crawl or bulk export. | Required: job_id (path) |
JSON with job state and progress. |
| Situation | Typical HTTP status | How to fix it |
|---|---|---|
Missing or malformed url | 400 | Send the full Meesho product URL, including https:// and the product ID. |
| Unsupported site or country value | 400 / 422 | Check site and country against the marketplaces confirmed for your account. |
| Missing or invalid API key | 401 | Send Authorization: Bearer <key> and check the key belongs to the right environment (sandbox or live). |
| Listing not found or no longer available | 404 or an empty record | Check the product ID and URL; the listing may have been removed or may be out of stock. |
| Request limit exceeded | 429 | Wait, then retry with backoff. Response headers show your remaining quota for the window. |
| Temporary processing failure | 5xx | Retry with exponential backoff; for large volumes use /v1/bulk instead of many synchronous calls. |
Status codes follow common REST conventions (429 is the one shown in our published dashboard example). The exact codes and error bodies are listed in the API reference supplied with your key.
Two common calls and what comes back. Illustrative sample data — not live product information.
curl -X POST https://api.webfusiondata.com/v1/product \
-H "Authorization: Bearer $WFD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://www.meesho.com/example-cotton-kurta/p/EXAMPLE123",
"country": "IN"
}'curl -X POST https://api.webfusiondata.com/v1/search \
-H "Authorization: Bearer $WFD_API_KEY" \
-d '{"site": "meesho", "query": "cotton kurta", "country": "IN"}'url or site + query select what to fetch; country selects the marketplace. The key stays in an environment variable — never hard-code it or ship it in client-side code.{
"product_id": "EXAMPLE123",
"marketplace": "IN",
"title": "Example Cotton Kurta",
"brand": "Example Brand",
"price": { "amount": 399.00, "currency": "INR" },
"discount": { "percent": 50, "list_price": 799.00 },
"availability": "Available",
"rating": 4.5,
"review_count": 1280,
"seller": "Example Seller",
"product_url": "https://www.meesho.com/example-cotton-kurta/p/EXAMPLE123",
"crawled_at": "2026-01-15T09:30:00Z"
}{
"query": "cotton kurta",
"result_count": 48,
"results": [
{ "title": "Example Cotton Kurta", "price": 399.00,
"rating": 4.6, "in_stock": true }
]
}The generic search sample on our Ecommerce Scraping API page uses a flat price number and an in_stock flag, while the product example above nests price under an object. The final Meesho schema is confirmed in your API reference.
Choose the marketplace with the country parameter. We do not claim global coverage: the marketplaces available to you are confirmed during onboarding, and requests outside that list are rejected rather than guessed.
| Marketplace | Meesho domain | Local currency | Status for the API |
|---|---|---|---|
| India | meesho.com | INR | Confirm at onboarding |
This is the site we expect to start with, not a coverage guarantee. Need anything else? Tell us and we will confirm feasibility.
Why it matters: the site fixes the currency (INR), the catalogue and which optional fields (discount, variants, delivery, payment options) appear. Meesho delivery details can depend on the pincode, so tell us if you need pincode-level data.
What is published today, and what we give you in writing before you go live. We do not publish numeric limits, latency or uptime figures on this page.
| Topic | How it works | Status |
|---|---|---|
| Authentication | Your API key is sent as a bearer token in the Authorization header. Use the sandbox key while testing. | Documented |
| Limits and concurrency | Per-minute limits and concurrent-request allowances scale with your plan; response headers show your remaining quota. Use /v1/bulk for very large volumes. | DocumentedNumbers: your plan |
| Validation and errors | Malformed or missing parameters are rejected with a standard HTTP error (see Endpoints), and responses are schema-checked before delivery. | Exact codes: API reference |
| Timeouts and retries | Set a client timeout and retry reads on 429 and 5xx with exponential backoff. Move long work to /v1/bulk and /v1/status/:job_id, and avoid blind retries of POST /v1/monitor or /v1/bulk. | Recommended practice |
| Pagination | Search returns a result_count and result list. Pagination for deeper results is scoped per project. | Confirm at onboarding |
| Usage monitoring | An account dashboard shows request volume, latency, success rate and job status. | Documented |
A Meesho API integration needs a request layer, somewhere to store results and a schedule. After that, the data can feed resale tools, databases, BI dashboards, reports and analytics pipelines.
Agree marketplaces, fields and refresh frequency, then call the sandbox with a few sample products.
Put authentication, timeouts and retry backoff in one small client module your whole team reuses.
Upsert records by product ID and marketplace, and keep every crawled_at timestamp to build a time series.
Use monitors and bulk jobs, act on webhooks, and connect the table to your dashboards and reports.
import os, sqlite3, requests
API = "https://api.webfusiondata.com/v1/product"
HEADERS = {"Authorization": f"Bearer {os.environ['WFD_API_KEY']}"}
def fetch(product_id):
body = {
"url": f"https://www.meesho.com/product/p/{product_id}",
"country": "IN",
}
r = requests.post(API, json=body, headers=HEADERS, timeout=60)
r.raise_for_status()
return r.json()
db = sqlite3.connect("meesho_prices.db")
db.execute("CREATE TABLE IF NOT EXISTS prices "
"(product_id TEXT, amount REAL, currency TEXT, at TEXT)")
for product_id in ["EXAMPLE123"]:
item = fetch(product_id)
db.execute("INSERT INTO prices VALUES (?, ?, ?, ?)", (
item["product_id"],
item["price"]["amount"],
item["price"]["currency"],
item.get("crawled_at"),
))
db.commit()Default response format for every endpoint.
Bulk export jobs delivered as CSV or XLSX to S3, GCS or your own bucket.
Callbacks when a job completes or a tracked value changes, plus recurring checks through /v1/monitor.
Managed warehouse connectors, client libraries and no-code paths.
Listed on the Ecommerce Scraping API page; availability for your Meesho scope is confirmed during onboarding. See also the AI Parser and ecommerce datasets. Related: product availability and MAP monitoring.
A REST API from WebFusion Data that returns Meesho product pages as structured JSON. Send a product URL, or a keyword and a marketplace, and get title, INR price, discount, rating, seller and availability. It shares endpoints with our Ecommerce Scraping API, so you never run proxies, browsers or parsers.
Core fields are product ID, title, category, price in INR, availability, images, product URL and a capture timestamp. Brand, discount, variants, rating, review count and seller come back where the page shows them. Delivery and payment details and review text are confirmed per project. See the data fields table.
Yes, through the URL. Meesho product links end in /p/ID, so you build each URL from your IDs and send it to /v1/product. The product ID is returned in the record for matching. Whether a dedicated ID parameter exists is confirmed at onboarding.
Yes. POST /v1/monitor registers a listing for scheduled price and stock checks with webhook alerts, and GET /v1/monitor/:id returns current values and recorded changes, which suits price and discount tracking. History starts at registration, so ask about a backfill or store each response with its crawled_at timestamp.
The seller shown on the listing, sizes and colours, and the delivery and payment details on the page are returned where displayed. Seller profiles, other offers and pincode-specific delivery are confirmed with you before you build on them.
We do not claim wide coverage. The country parameter selects the marketplace, and the Indian site, meesho.com, is the starting point. Tell us what you need and we will confirm it at onboarding. See the supported marketplace.
Each request carries your API key as a bearer token in the Authorization header. Every account includes a sandbox for testing with sample responses. Keep the key on your server, in an environment variable or secrets manager, and never in client-side code.
JSON is the default for all endpoints. Bulk export jobs can also be delivered as CSV or XLSX, to S3, GCS or your own bucket. Webhooks, SDKs and database push options are described in Integration and Data Delivery.
Use the Request API Demo button or the form below and tell us the marketplaces, product volume, fields, refresh frequency and delivery format you need. We confirm the scope and set up access, including the sandbox. You can also email sales@webfusiondata.com or book a consultation.
At WebFusionData, we specialize in cutting-edge web scraping solutions to help you unlock valuable insights and drive business growth. Whether you need custom data extraction, real-time monitoring, or large-scale web scraping, our team is here to assist you.
Ready to get started? Contact us for a personalized quote.