Instacart Rate Limits
Instacart throttles per second and publishes no number. Both the Developer Platform and the Connect error references define HTTP 429 as "the number of your requests has exceeded the rate limit for requests per second", and neither states what that rate is. There is no published quota, no burst allowance, and — the part that matters most for an automated client — no rate-limit response headers of any kind. No X-RateLimit-*, no RateLimit-*, no Retry-After. A caller cannot read its remaining budget or learn when to come back; it can only observe the rejection and guess. Persistent 429s are a conversation with your Instacart representative, not a self-service tuning exercise.
Instacart Rate Limits is the machine-readable rate-limit profile for Instacart on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests_per_second and not published.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, serviceUnavailable, and timeout.
Tagged areas include Grocery, E-Commerce, Marketplace, and Rate Limiting.
Limits
Policies
Sources
- https://docs.instacart.com/developer_platform_api/api/error_and_status_codes
- https://docs.instacart.com/connect/api/error_and_status_codes
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.