Custom scraper

Instacart Scraper

We do not have a dedicated Instacart data API. What we do have is an AI scraper that reads an instacart.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.

  • instacart.com
Three stages of an Instacart run: paste an instacart.com URL billed from the plain page price of EUR 0.15 per 1,000 pages; declare columns such as product_title and brand; and the 12 columns it returns.

How to scrape Instacart

Instacart 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. Instacart republishes other retailers' catalogues at its own markup, so it shows what a delivered price looks like against the same item in store. The way to get the data is to read the page the way a customer sees it. Prices here are set per store, so a row is only meaningful with the store it came from attached, and a scrape that ignores store selection is quietly averaging several different markets.

How instacart.com is laid out

What a run needs to know about Instacart before you pick the URLs.

  • The price depends on the retailer

    Instacart shows each retailer's storefront separately. Some retailers offer everyday store prices on Instacart, others mark prices up.

  • The storefront tells you

    Each storefront states its pricing policy, such as "Everyday store prices", "See pricing policy" or "Higher than in-store prices". Capture that label with every price.

  • Fees come on top

    Delivery fees, service fees and tips are added at checkout. The item price is not the order cost.

  • Location matters

    Prices and availability depend on the delivery address and the store that serves it. Pin the address.

  • Not the retailer's own price

    Because of markups, an Instacart price is not evidence of a retailer's shelf price. Compare against the retailer's own site where possible.

What the AI scraper does with an instacart.com link

The same three steps as any other page you point it at. Nothing about Instacart is pre-built, which is exactly why it works on pages nobody wrote a connector for.

  1. Paste the link

    Give it an instacart.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.

  2. 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.

  3. 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.

  1. Set it up once

    Add your ASINs, keywords, places or apps to a scraper in the web app. New accounts get 5 free requests.

  2. 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.

  3. Saved in your database

    Each run adds dated rows, so this week sits next to last week. Rows are kept for 90 days.

  4. 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.

You give
  • Link to an Instacart pagerequired

    Open the product or category page in your browser and copy the address. Any Instacart country domain works the same way.

    https://www.instacart.com/
  • Your column listrequired
    product_title, brand, store_id, pack_size
  • How often it runsoptional
    Daily at 06:00 UTC
You get

One row per product for the selected store, 12 columns each

  • product_title
  • brand
  • store_id
  • pack_size
  • price
  • unit_price
  • unit
  • loyalty_price
  • currency
  • 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 Instacart run comes back with

We are not going to print a table of invented grocery (store-level pricing) prices and call it real output. Instacart did not return a readable product page to an ordinary request, 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_titleProduct title as the retailer writes it
brandBrand as the retailer labels it
store_idWhich store or ZIP this price was quoted for
pack_sizePack size as printed
priceShelf price for that store today
unit_pricePrice per unit, where the page prints it
unitWhich unit that per-unit price is quoted in
loyalty_priceMember or card price, where the page shows one
currencyCurrency the page quoted
availabilityWhether the line is in stock at that store
product_urlLink back to the page the row came from
checked_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 Instacart page costs

Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count. The price shown is the starting price: €0.15 per 1,000 plain pages. If a run needs a browser render it costs €0.75 per 1,000 pages.

€0.15per 1,000 pagespay-as-you-go, no plan

Measured on 3 October 2026, not assumed. A plain HTTP request for an instacart.com page comes back with the page, so most runs never need a browser and never need a residential exit.

Worked example

500 Instacart pages checked once a day for a month is 15,000 pages.

about EUR 2.25 for the month at the plain page price, about EUR 11.25 if the pages need a browser render

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 Instacart 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.

Store is part of the price

The field most grocery scrapes omit and then cannot explain their own numbers without.

  • Which store or ZIP the price was quoted for
  • Shelf price for that store
  • Member or loyalty price where shown
  • Whether the line is in stock at that store
  • Pickup or delivery availability, where the page shows it

Unit price, not shelf price

Still the only number that compares across brands, and still printed in small type.

  • Pack size exactly as printed
  • Price per unit where the page prints it
  • Which unit the per-unit price is quoted in
  • Multibuy or promotional price where shown
  • Any was-price the page prints

Product identity

Own-label lines carry no manufacturer identifier, so the retailer's own code is the join key.

  • Retailer's own product code
  • EAN or GTIN, where published
  • Brand, or own-label name
  • Category breadcrumb
  • Product image URLs

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 Instacart publishes them.

What people use Instacart data for

01

Store-level price mapping

The same line at two of this retailer's own stores is frequently two different prices. A store column turns that from an anecdote into a map, and it is the input regional pricing actually needs.

02

Unit-price comparison across retailers

One schema with pack size and per-unit price across several grocers turns shelf prices into a table that genuinely compares.

03

Promotion calendar reconstruction

When a promotion starts, how deep it goes, how long it runs, and whether it runs everywhere or only in some stores.

04

Loyalty-price visibility

Member prices are a second price list sitting next to the first one. Capturing both is the difference between modelling the shelf and modelling what shoppers pay.

05

Availability and delisting alerts

Suppliers usually find out a line has been delisted weeks late. A daily check against a store list tells you in a day.

What makes Instacart harder than an ordinary storefront

Here is what the scraper is actually up against on instacart.com, measured rather than assumed.

Access

  • Plain HTTP requests are answered, but the answer is the shell of the page rather than the priced version of it
  • No named protection vendor on the response, which is why this one lands on a cheaper tier than most of the cohort
  • robots.txt carries a blanket disallow, so the scheduling decision is yours to make and document

There is no single price

  • Price is set per store, so the store or ZIP has to be part of the input and part of every row
  • Store selection is usually held in a cookie or a session, so a run has to be pointed at a store-scoped URL rather than a generic one
  • Covering several stores multiplies the page count, which is what drives the cost
  • Member and loyalty prices sit alongside shelf prices and are a separate column, not a replacement for one

What the page publishes

  • Structured data is published but not at product level (Answer, EntryPoint, FAQPage), so price comes from the rendered page rather than a feed
  • Prices carry a platform markup that varies by retailer, so an Instacart price is never the retailer's own price.
  • 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 instacart.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.

  • Instacart has one specific trap

    Prices carry a platform markup that varies by retailer, so an Instacart price is never the retailer's own price.

FAQ

Instacart scraping — questions

What people ask before pointing the scraper at instacart.com.

Instacart 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 Instacart data into your stack?

Start free — or talk to our team about your exact fields, refresh cadence and volume.