Grocery price and availability monitoring
Usa los endpoints de Instacart para convertir grocery price and availability monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
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.
Familias de endpoints
6
Parámetros documentados
21
Ejemplos
6
Snapshot en vivo del catálogo
Endpoints activos
6
Métodos
GET
Parámetros obligatorios
21
Referencias de esquema
6
{
"platform": "Instacart",
"endpoint": "instacart-stores",
"method": "GET",
"path": "/instacart/stores",
"auth": "apiKey"
}Casos de uso
Find nearby Instacart stores, get product detail and pricing, and search for products by keyword as structured JSON.
Usa los endpoints de Instacart para convertir grocery price and availability monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Instacart para convertir store coverage and delivery-eta tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Instacart para convertir product search and category research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Instacart — 6 endpoints, 21 parámetros de solicitud documentados y 6 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
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.
Mapa de cobertura
/instacart/departments
/instacart/item
/instacart/search
/instacart/search-nearby
/instacart/stores
/instacart/trending
Catálogo de endpoints
/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.
Notas de la respuesta
- `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.
Herramienta MCP 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.
Notas de la respuesta
- `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.
Herramienta MCP 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.
Notas de la respuesta
- 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.
Herramienta MCP 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.
Notas de la respuesta
- 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.
Herramienta MCP 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.
Notas de la respuesta
- `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.
Herramienta MCP 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.
Notas de la respuesta
- 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.
Herramienta MCP instacart_departments
APIs relacionadas
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Cobertura de la empresa
Maplebear Inc. · CART
Instacart es operado por Maplebear Inc. (CART). Los endpoints SEC de Crawlora usan el mismo CIK de esa empresa, así que los filings, datos financieros, transacciones de insiders y participaciones 13F provienen de la misma API key que los endpoints de Instacart de arriba.
API de filings y datos financieros SEC →Cómo hacer scraping de 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
Instala un agent skill de Crawlora y tu agente obtiene datos de Instacart como JSON mediante la API documentada, sin escribir un scraper. Estos skills cubren Instacart:
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-researchPreguntas frecuentes
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.