Mercari Scraper
We do not have a dedicated Mercari data API. What we do have is an AI scraper that reads a mercari.com page you point it at, turns it into the columns you asked for and hands them back by REST, CSV or Excel — on a schedule, priced per page.
- mercari.com
How to scrape Mercari
Mercari publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface. Mercari is where a brand finds out what its product is worth once it leaves the channel, which matters for warranty, grey-market and MAP work. The way to get the data is to read the page the way a customer sees it: point the AI scraper at a mercari.com URL, declare the columns you want in plain English, and schedule it. On a resale platform the number that matters is what something actually sold for, and the live asking price is only a proxy for it.
What the AI scraper does with a mercari.com link
The same three steps as any other page you point it at. Nothing about Mercari is pre-built, which is exactly why it works on pages nobody wrote a connector for.
Paste the link
Give it a mercari.com product or listing URL. Market, currency and assortment all come from the page itself, so there is no region setting to get wrong — the URL decides.
Declare the columns
Name each field, give it a type and write a line telling the AI what to look for. “product_title” and “brand” are the two most people start with. The schema is yours and you can change it between runs.
Schedule it and collect
Run it hourly, daily or on demand. Every run returns the same columns in the same order with a timestamp on each row, so the history builds itself.
Set it up once. The data keeps coming.
Save your search once and it runs by itself. Every run lands in your own Scrapewise database, and you pick how to read it.
Set it up once
Add your ASINs, keywords, places or apps to a scraper in the web app. New accounts get 5 free requests.
Runs on your schedule
Pick daily, weekly on the days you choose, every few days, or the first or last day of the month. Scheduled runs start at night, European time. Need it more often? Start runs from your own code.
Saved in your database
Each run adds dated rows, so this week sits next to last week. Rows are kept for 90 days.
Use it your way
Open the table in the web app and download the latest run as an Excel file. Ask your own AI assistant about it. Or pull the rows into your code with an API key.
Ask your AI assistant about your own data
Connect Claude Desktop or Claude Code with a read-only key. The assistant reads the rows you've already collected, at no extra cost on Scrapewise. With a full-access key it can start a run for you too.
- Which of my ASINs lost the Buy Box this week?
- Which competitor cut prices the most since Monday?
- Show the keywords where I dropped out of the top 10.
What you send and what you get
You send a link and a column list. Everything else — market, currency, which products are on the page — comes from the page, so there is nothing to configure twice.
- Link to a Mercari pagerequired
Open the product or category page in your browser and copy the address. Any Mercari country domain works the same way.
https://www.mercari.com/ - Your column listrequired
Field name, type and one line of plain English per column. Written once, reused on every run.
product_title, brand, size, condition - How often it runsoptional
Hourly, daily, weekly or on demand through the API. Daily is what most price monitoring uses.
Daily at 06:00 UTC
One row per listing, 11 columns each
- product_title
- brand
- size
- condition
- ask_price
- last_sale_price
- currency
- seller_name
- availability
- product_url
- checked_at
REST API, CSV or Excel. The column set stays the same between runs, so downstream jobs do not re-map fields.
The columns a Mercari run comes back with
We are not going to print a table of invented resale marketplace prices and call it real output. Mercari answers an ordinary request with Cloudflare rather than a product page, so we have no run of our own to quote from. So what is published here is the column list you declare before the run, which is the same list every run comes back with.
product_titleListing title as the platform shows itbrandBrand as the listing labels itsizeSize or variant the listing is forconditionCondition the seller declaredask_priceWhat the seller is asking todaylast_sale_priceMost recent sale price, only where the page prints onecurrencyCurrency the page quotedseller_nameSeller behind the listing, where shownavailabilityWhether the listing is still liveproduct_urlLink back to the page the row came fromchecked_atWhen this run collected the page (UTC)Every column here is one you name yourself in the schema. If a field is not on the page on the day of the run, it comes back empty rather than guessed.
What a Mercari page costs
Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count.
Measured on 3 October 2026, not assumed. A plain request for a mercari.com page is refused with HTTP 403 by Cloudflare, and so is the bare homepage, which rules out a bad path as the explanation. Clearing that needs both a real browser and a residential exit.
500 Mercari pages checked once a day for a month is 15,000 pages.
about EUR 56.25 for the month
You are charged for what a run actually used, not what it was expected to need, and your balance never expires.
See the full price list →What this page is not promising
We would rather say this here than in a support ticket.
No dedicated Mercari endpoint
There is no Mercari API in our catalogue and no pre-built Mercari schema. The AI scraper reads the page you point it at — that is the whole mechanism, and it is why it works on pages nobody built a connector for.
Nothing behind a login
It reads what a visitor can see. Account pricing, contract pricing and anything behind a sign-in are out of scope.
No field the page does not show
If the page does not print it, the scraper cannot return it. Identifiers like EAN or GTIN only come back where the retailer publishes them.
A price is a point in time
Every row carries the timestamp of the run that collected it. A price without one is not evidence, which is why the column is in the default schema.
Mercari has one specific trap
Condition is free text rather than a grade, so comparing a Mercari price to a retail price means normalising condition before the numbers mean anything.
Not a bulk dump of the catalogue
You give it the URLs you care about. It does not crawl mercari.com end to end, and a schedule that tried to would cost more than the answer is worth.
Typical fields the AI scraper extracts from a Mercari page
Treat this as a starting point rather than a fixed schema. What comes back is whatever the page actually shows on the day of the run.
Asking price against realised price
Two different numbers that get confused constantly. A seller's ask tells you what they hope for; a last sale tells you what the market paid.
- Current asking price
- Last sale price, only where the page states one
- Lowest ask and highest bid, where the platform publishes them
- Currency the page quoted
- Whether the listing is still live
Condition and size, which set the price
On resale the same model at two conditions is effectively two products, and most price tools collapse them into one.
- Condition as the seller declared it
- Size or variant
- Whether the item is described as new, used or deadstock
- Box or packaging condition, where the listing says
- Photographs attached to the listing
Who is selling
Resale supply is individuals and small shops, so the seller is part of the price.
- Seller name or handle
- Seller rating and sales count, where shown
- Location the listing ships from
- Delivery charge quoted
- How long the listing has been up, where the page says
The column list is one you write: name each field, give it a type and a line telling the AI what to look for. The schema belongs to your run, not to us. How Custom Schema works →
What it cannot give you If a field is not visible on the page, the scraper cannot invent it. Identifiers such as EAN or GTIN only come back when Mercari publishes them.
What people use Mercari data for
Secondary-market price discovery
What your product, or a competitor's, actually changes hands for after release. Brands price the first sale; the resale market prices everything after it, and that number is public.
Spotting counterfeit and grey-market supply
A model listed well below every other listing, repeatedly, from the same handful of sellers, is a pattern. You only see the pattern if you are collecting the listings daily.
Demand signal before you reorder
Resale prices above retail are the clearest demand signal there is, and they move days before your own sell-through data does.
Condition-adjusted valuation
A used-versus-new price spread per model, built from real listings, is what trade-in and buy-back pricing needs and what no vendor will sell you.
Feeding your own pricing rules
The export is a normal REST API or CSV, so it drops straight into whatever valuation or repricing logic you already run.
What makes Mercari harder than an ordinary storefront
Here is what the scraper is actually up against on mercari.com, measured rather than assumed.
Access
- Plain HTTP requests are refused at the edge — a naive fetch returns HTTP 403, not a page
- Named protection on the response: Cloudflare
- robots.txt carries a blanket disallow, so the scheduling decision is yours to make and document
Asks, bids and sales are three things
- The live asking price is not the market price, and the two can sit far apart for weeks
- Condition and size split one model into many effectively separate products
- Listings disappear the moment they sell, so a weekly check silently loses the interesting rows
- Sold-price history is rarely on the public page, so a curve has to be built by collecting daily
What the page publishes
- No product-level structured data is published, so every field is read off the rendered page
- Condition is free text rather than a grade, so comparing a Mercari price to a retail price means normalising condition before the numbers mean anything.
- Price is one of the last things the page settles on, so a read taken too early records the placeholder rather than the number
Keeping a history
- A single read is a snapshot; the value is in the series, which means the run has to be scheduled and the rows kept
- Every row carries the timestamp of the run that produced it, so two days can be compared without guesswork
- Columns stay stable between runs, so a dashboard written once does not break when the site redesigns
Mercari scraping — questions
What people ask before pointing the scraper at mercari.com.
Mercari publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface.
Ready to pull Mercari data into your stack?
Start free — or talk to our team about your exact fields, refresh cadence and volume.