How does a product data API work?
Your system sends a request with a product ID or a public page link and the source, such as Amazon or Flipkart. Our data service reads the public product page at a gentle pace, turns it into named fields such as title, price, seller and stock, checks that each field has the right type, and sends the result back as JSON. The same data can also land as a row in Google Sheets, or be pushed to your webhook only when something changes.
The manual way, and what goes wrong
Teams that need marketplace data often copy it by hand: open the listing, note the price, seller and stock, paste it into a sheet. It is slow, it stops when the person is busy, and the sheet ends up with prices in three formats and products named five ways.
Home-made scripts break quietly. A site changes its layout, the script keeps running, and the sheet fills with empty cells or, worse, yesterday’s value presented as today’s. Nobody notices until a decision was made on wrong data.
What happens, step by step
- Your system sends a request. With a product ID or a public link, and the source. Each request carries an API key, so only your systems can use it.
- The public page is read. At a gentle pace, without logging in, from Amazon, Flipkart, Meesho, Myntra, Nykaa, a public Shopify store and other sources we agree on.
- It is parsed and cleaned. Prices become numbers, currencies are named, and products keep their marketplace IDs, so a renamed listing is still the same item.
- Fields are checked. Missing or odd values are marked with a reason instead of being guessed or filled from an earlier run.
- The data is delivered. As JSON, as a row in Google Sheets, or as a webhook to your own system when something changed.
What you get
- A documented API with the same field names on every call and from every source.
- JSON, sheet rows or webhooks, whichever your team uses.
- History of each run, so you can chart prices and stock over time.
- Clear errors and partial results when a page cannot be read.
- Alerts to our team when a source changes, so the collector is fixed.
What you need to provide
- The products, pages or searches you want data for.
- The fields you need, and how often they should refresh.
- Where the data should go: your app, a sheet or a webhook address.
- For your own seller or store data, access to the official API.
Which tools can be swapped?
| Part | Options |
|---|---|
| Source | Amazon, Flipkart, Meesho, Myntra and Nykaa in the demo. Public Shopify stores, public job listings and public social posts can be added. |
| Deliver as | JSON from our API, a row in Google Sheets, or a webhook to your system. |
| Refresh | On request, on a schedule, or only when a value changes. |
Limits, and when it is not a good fit
- Public data only. Anything behind a login, or anything a site’s rules do not allow, is out of scope.
- Sites change their pages. When that happens, some fields can come back empty for a short time until the collector is updated. You see the gap; you never get an old value presented as new.
- Very large volumes or very frequent refreshes need their own plan and a conversation about cost.
- It is not legal advice. For unusual uses of collected data, check with your own lawyer.
Public data only
The API collects what any shopper can see without logging in, within each site’s rules and at a pace that does not affect the site. It never uses someone else’s account and avoids personal data that is not needed. When you have access to an official API for your own data, such as the Amazon Selling Partner API for your seller account or the Shopify Admin API for your store, we use that instead, because it is more reliable and clearly within the rules.
Questions about this automation
Which fields does the product data API return?
Typically the marketplace ID, title, price, MRP, currency, seller, rating count, stock status and the time it was fetched. Extra fields such as variants, images or delivery dates can be added when they are public on the page.
Do you have an Amazon product data API for India?
Yes, for public listing data on Amazon.in and other marketplaces, by ASIN or link. For your own seller data, such as orders and fees, we connect to the Amazon Selling Partner API with your permission instead.
What happens when a product page changes its layout?
The affected field comes back empty with a reason, the result is marked as partial, and our team is alerted to update the collector. The API never fills the gap with an earlier value.
Can I get the data in Google Sheets without writing code?
Yes. The same fields can be written as rows in a Google Sheet on a schedule, with one row per product per run, so you build a history without any code.
How often can the data be refreshed?
From on request to several times a day, depending on the source and how many products you track. Faster refreshes cost more, so we match the schedule to how often the data really changes.