REI Scraper
We do not have a dedicated REI data API. What we do have is an AI scraper that reads a rei.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.
- rei.com
How to scrape REI
REI 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. REI is the US outdoor price reference and the benchmark for what a non-discounted outdoor price looks like. The way to get the data is to read the page the way a customer sees it. Sport and outdoor ranges are seasonal and size-run driven, so the markdown calendar and which sizes survive it carry more information than the shelf price.
How rei.com is laid out
What a run needs to know about REI before you pick the URLs.
Outlet items sit in the same lists
Search results mix full-price items with ones marked REI OUTLET, each with Save x% compared to a reference price. Capture the outlet flag on every row.
Seconds are separate products
Items with cosmetic flaws are sold as Seconds, as separate products with their own prices. Do not merge them with the first-quality item.
Member rewards
REI membership is a one-time lifetime fee, and members earn a 10% Co-op Member Reward on eligible full-price purchases, plus member coupons. The public price is what non-members pay.
Sales with end dates
Sale items can show a date such as Sale Ends May 25. Store the date with the price.
REI Co-op own brand
REI sells hundreds of its own REI Co-op products, which have no direct competitor listing. Match them on specification, not on name.
What the AI scraper does with a rei.com link
The same three steps as any other page you point it at. Nothing about REI is pre-built, which is exactly why it works on pages nobody wrote a connector for.
Paste the link
Give it a rei.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. “brand” and “product_title” are the two most people start with. The schema is yours and you can change it between runs.
Schedule it and collect
Run it daily, weekly 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 an REI pagerequired
Open the product or category page in your browser and copy the address. Any REI country domain works the same way.
https://www.rei.com/ - Your column listrequired
brand, product_title, sku, colour - How often it runsoptional
Daily at 06:00 UTC
One row per product on the page, 12 columns each
- brand
- product_title
- sku
- colour
- price
- was_price
- discount_percent
- currency
- sizes_in_stock
- 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 an REI run comes back with
We are not going to print a table of invented sport and outdoor prices and call it real output. REI does not answer an ordinary request at all, 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.
brandBrand as the site labels itproduct_titleProduct title as the site writes itskuSite's own product codecolourColourway the page is showingpricePrice the site is charging todaywas_priceStrike-through price, only where the page shows onediscount_percentMarkdown percentage, as the page states itcurrencyCurrency the page quotedsizes_in_stockSizes the page shows as still availableavailabilityStock state as the page states itproduct_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 an REI page costs
Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count.
Measured on 3 October 2026, not assumed. REI did not answer a plain request at all — the connection is dropped rather than refused, which is the most restrictive case and the one that needs the full stack.
500 REI 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 →Typical fields the AI scraper extracts from an REI 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.
Season and markdown
Outdoor ranges are bought in for a season and cleared at the end of it, so the markdown curve is the pricing story.
- Current price
- Strike-through price where shown
- Markdown percentage as stated
- Sale or clearance badge wording
- Currency the page quoted
Size run and colourway
A technical product at a deep discount with one size left is clearing, not competing.
- Sizes still available
- Colourway the page is showing
- Whether the variant is sold out entirely
- Which sizes are listed at all
- Delivery window shown
Specification and identity
Outdoor buyers compare on specification, and the specification table is usually rendered on the page.
- Brand and model name
- Site's own product code
- Manufacturer part number, where printed
- Technical specification table, where rendered
- Category breadcrumb
- Rating and review count, where shown
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 REI publishes them.
What people use REI data for
Season-end markdown tracking
When clearance starts, on which lines and how deep. That calendar repeats each year and is only visible if you collected it last year.
Size availability as a demand signal
Sizes disappearing at full price is the closest public proxy for sell-through on a technical range.
Brand price-floor checks
If you make outdoor or sports gear, this is how you see what your products are actually listed at across the retailers that carry them.
Cross-retailer specification comparison
Where pages publish part numbers and specification tables, one schema across retailers produces a table that genuinely joins.
Range and assortment research
What a category carries, at what price points, from which brands, before you commit to a buy.
What makes REI harder than an ordinary storefront
Here is what the scraper is actually up against on rei.com, measured rather than assumed.
Access
- Plain HTTP requests are dropped rather than answered, so there is nothing to parse
- No named protection vendor on the response, which is why this one lands on a cheaper tier than most of the cohort
- No usable sitemap directive in robots.txt, so the URL list comes from your own category pages
Seasonal ranges and size runs
- Colourways are often separate URLs with their own stock and sometimes their own price
- Size availability moves daily and independently of price
- Clearance lines appear and disappear within days, so a weekly check loses the interesting rows
- Category pages are lazily loaded and paginated, so a sweep is a list of URLs rather than one request
What the page publishes
- No product-level structured data is published, so every field is read off the rendered page
- The outlet carries the same brands at different prices on a separate path, so the two have to be read separately.
- Price is one of the last things the page settles on, so a read taken too early records the placeholder rather than the number
What to watch on rei.com
The one thing specific to this site. The general limits — public pages only, no field the page does not show, your URLs rather than a full crawl — are in the custom scrapers FAQ.
REI has one specific trap
The outlet carries the same brands at different prices on a separate path, so the two have to be read separately.
REI scraping — questions
What people ask before pointing the scraper at rei.com.
REI 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.
Questions that apply to every site — scheduling, exports, what it will not do — are answered in the custom scrapers FAQ.
Ready to pull REI data into your stack?
Start free — or talk to our team about your exact fields, refresh cadence and volume.