Grocery price and availability monitoring
Mit Instacart-Endpunkten verwandelst du grocery price and availability monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn public Instacart pages into structured grocery data — nearby stores by postal code (with EBT acceptance and delivery ETA), single-product detail with live pricing and nutrition, keyword search within a store or across every nearby retailer at once, trending searches, and a store's department taxonomy, all as normalized JSON. Credential-free.
Find nearby Instacart stores, get product detail and pricing, and search for products by keyword as structured JSON.
Endpunkt-Familien
6
Dokumentierte Parameter
21
Beispiele
6
Live-Katalog-Snapshot
Aktive Endpunkte
6
Methoden
GET
Pflichtparameter
21
Schema-Referenzen
6
{
"platform": "Instacart",
"endpoint": "instacart-stores",
"method": "GET",
"path": "/instacart/stores",
"auth": "apiKey"
}Use Cases
Find nearby Instacart stores, get product detail and pricing, and search for products by keyword as structured JSON.
Mit Instacart-Endpunkten verwandelst du grocery price and availability monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Instacart-Endpunkten verwandelst du store coverage and delivery-eta tracking in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Instacart-Endpunkten verwandelst du product search and category research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Instacart-Endpunktkatalog — 6 Endpunkte, 21 dokumentierte Request-Parameter und 6 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
6 documented Instacart endpoints, grouped into 6 request families — Departments, Item and Search, plus 3 more.
21 request parameters are documented across those Instacart endpoints, 21 of them required — the full input contract is public before you write any integration code.
6 of the 6 Instacart endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
Instacart endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
6 hosted MCP tools back the Instacart endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/instacart/departments
/instacart/item
/instacart/search
/instacart/search-nearby
/instacart/stores
/instacart/trending
Endpunktkatalog
/instacart/storesFinds Instacart retailer storefronts (grocery stores, warehouse clubs, and other partner retailers) serving a US postal code, each with the identifiers needed to look up its items and search suggestions. Public data sourced from Instacart's own store-discovery API.
Hinweise zur Response
- `shop_id`, `store_slug` (the store's `slug` field), and `retailer_location_id` from a result are the values [`GET /instacart/item`](instacart-item.md) and [`GET /instacart/search`](instacart-search.md) need. - Results cover every retailer partnered with Instacart in the area, not just grocery — warehouse clubs and specialty retailers are included. - `accepts_ebt`, `saver_store`, and `delivery_eta` are best-effort enrichment fetched after the base store list. A failure fetching either does not fail the request — those fields are simply omitted for the affected stores.
MCP-Tool instacart_stores
/instacart/itemReturns a single product's detail at a specific Instacart store: name, size, brand, image, current pricing (with any sale/offer badge), availability, stock level, dietary labels, and nutrition facts. Public data sourced from Instacart's own storefront pages.
Hinweise zur Response
- `price` is only fully populated once the underlying request has an active store session — this endpoint handles that automatically, but a first call for a given store can take slightly longer while that session is established. - `on_sale` and `offer_label` are only present when the item currently has a promotion.
MCP-Tool instacart_item
/instacart/searchReturns Instacart's own search-term autosuggestions for a keyword within one store -- the same suggestion list shown in the site's own search box dropdown. This is term-level (matching search phrases plus a representative thumbnail), not a paginated product-results list. Public data sourced from Instacart's own storefront search.
Hinweise zur Response
- Each suggestion's `relative_url` links to that term's search-results page on instacart.com (not itself part of this API's contract, since that page's own product-listing data isn't exposed here). - A genuine zero-match query returns `suggestions: []` with a `200`, not an error.
MCP-Tool instacart_search
/instacart/search-nearbyReturns Instacart's own search-term autosuggestions for a keyword across every retailer serving a postal code at once, rather than one specific store. Public data sourced from Instacart's own cross-retailer search.
Hinweise zur Response
- Unlike single-store search, this endpoint does not need any store context — only a postal code and a query. - A genuine zero-match query returns `suggestions: []` with a `200`, not an error.
MCP-Tool instacart_search_nearby
/instacart/trendingReturns Instacart's own popular/trending search terms across every retailer serving a postal code -- the same blank-state suggestions shown before a user types anything into the search box. Public data sourced from Instacart's own cross-retailer search.
Hinweise zur Response
- `terms` does not carry a `relative_url` field (unlike [`GET /instacart/search`](instacart-search.md) and [`GET /instacart/search-nearby`](instacart-search-nearby.md)'s suggestions) — popular terms are not tied to a specific search-results page link.
MCP-Tool instacart_trending
/instacart/departmentsReturns a store's department/category taxonomy (Produce, Dairy & Eggs, Bakery, ...) two levels deep -- department and subcategory. Metadata only, does not return products. Public data sourced from Instacart's own storefront navigation.
Hinweise zur Response
- The taxonomy may include a small number of non-food, promotional or internal groupings alongside real departments (e.g. an "Evergreen VC" entry seen live) — these are passed through as returned rather than filtered, since there is no reliable documented signal to distinguish them from real departments. - This endpoint returns the taxonomy only, not products within a department.
MCP-Tool instacart_departments
Verwandte APIs
Marketplaces & Retail
Separate an auction that is still open from a completed sale, and use BaT's own make and model directory to carry valid IDs into search and price-history requests.
Marketplaces & Retail
Treat Glovo as a local marketplace: discover the supported city first, then follow that city's category, store, menu, and collection identifiers through the catalog.
Marketplaces & Retail
Use PetSmart's hierarchical paths to scope product searches, then keep product SKU, price range, online availability, pickup eligibility, and store inventory as separate fields.
Unternehmensabdeckung
Maplebear Inc. · CART
Instacart wird von Maplebear Inc. (CART) betrieben. Crawloras SEC-Endpunkte nutzen dieselbe CIK dieses Unternehmens, sodass Filings, Finanzdaten, Insider-Transaktionen und 13F-Beteiligungen mit demselben API-Key wie die Instacart-Endpunkte oben abrufbar sind.
SEC-Filings & Finanzdaten-API →So scrapst du Instacart
Crawlora's Instacart endpoints return store discovery, product detail, and search as normalized JSON with one API key — no login or account required. A pull on 2026-10-27 for ZIP 10001 returned 326 stores and 10 trending search terms, and showed that item routes need several ids from the store row.
Send a postal code to /instacart/stores for nearby retailers, each with EBT acceptance and a delivery ETA.
Pass a store's shop_id and slug plus a product_id to /instacart/item for live pricing, availability, and nutrition.
Search within one store via /instacart/search, or across every nearby retailer at once via /instacart/search-nearby.
Use /instacart/departments for a store's category taxonomy, or /instacart/trending for popular searches near a postal code.
stores returned 326 stores for 10001. The first was Costco with shop_id 968, retailer_location_id 284, retailer_id 5, service type delivery, EBT acceptance and an ETA string (By 12:45pm).
departments, search and item calls need shop_id plus store_slug (and retailer_location_id for items), so store all of them from the stores row. trending for 10001 returned 10 terms, starting with hershey.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft Instacart-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken Instacart ab:
Researches restaurants and grocery/food delivery via the Crawlora API — Yelp reviews, OpenTable reservations, DoorDash and Uber Eats restaurant…
npx skills add github.com/Crawlora-org/crawlora-skills --skill restaurant-food-delivery-researchFAQ
Send a postal code to Crawlora's /instacart/stores endpoint and get nearby retailer storefronts — name, EBT acceptance, delivery ETA — as structured JSON.
No Instacart account or login is required from the caller — only your Crawlora API key.
Yes — /instacart/item returns a product's current price, any active sale, availability, and nutrition facts at a specific store as structured JSON.
Not for general signup. Instacart's Developer Platform API is invite-only, and the average time from an access request to a demo approval and production key is about 30-40 days — there's no instant self-serve path. Crawlora's Instacart endpoints return store discovery, product detail with live pricing, and search data as structured JSON with a single API key, active immediately.
326 for 10001 on 2026-10-27. Store location is part of the key, so keep the postal code with the data.