instacart · Rate Limits

Instacart Rate Limits

Instacart Connect APIs are throttled per-second. Exceeding the per-second threshold returns HTTP 429 ("Too many requests"). Specific per-second numbers are not published in the public Connect documentation; partners with persistent 429s are directed to contact their Instacart representative. All requests must use HTTPS; HTTP requests are rejected.

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 1 rate-limit definition, measuring requests_per_second.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Grocery, E-Commerce, Marketplace, and Rate Limiting.

1 Limits Throttle: 429
GroceryE-CommerceMarketplaceRate Limiting

Limits

Per-second request threshold partner
requests_per_second
per-second threshold (exact value not publicly published)

Policies

HTTPS Required
All requests must use HTTPS; HTTP requests are rejected.
Backoff Strategy
On HTTP 429, clients should back off and retry with exponential backoff and jitter; persistent throttling should be raised with the Instacart partner representative.
Backward Compatibility
New fields are additive and optional; deprecated fields remain functional for at least six months with advance notice in the changelog.
Encoding and Types
Strings are UTF-8 without enforced length limits; integers default to int64.
Fair Use
Throttling is designed to allow legitimate traffic while preventing denial-of-service.

Sources