Distinguish Instacart's Developer Platform (IDP) from Instacart Connect before building a recipe/shopping-list integration, since IDP hands off fulfillment rather than executing it directly
domain: docs.instacart.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm which product you actually need: Instacart Connect is for retailers to receive and fulfill orders; IDP is for third-party publishers (recipe sites, content apps) to let users build a shopping list or recipe that deep-links into the Instacart app for checkout
Use the IDP Create Shopping List Page or Create Recipe Page endpoints to generate a URL that opens the Instacart app (or web fallback) with items pre-populated
Do not expect a direct 'place order' or fulfillment-status API in IDP — once the user follows the deep link, checkout, retailer selection, and fulfillment happen entirely inside Instacart's own app/session
Use brand_filters and health_filters to influence product matching, understanding that Instacart's matching engine — not your app — makes the final product selection at checkout
Request API keys through Instacart's developer platform onboarding; access has historically required going through an Instacart representative rather than being instantly self-serve
Known gotchas
IDP has no SKU-level item selection — you send product names/quantities and Instacart's matching decides the actual product, so exact-SKU guarantees are not possible
A single API key may only be scoped to one IDP endpoint (e.g., products_link but not recipe); request multiple keys if you need both
Because IDP hands off to Instacart's own checkout, you get no direct visibility into whether the user completed the order — don't design an integration that assumes order-status callbacks
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?