Dutchie · Rate Limits

Dutchie Rate Limits

Dutchie does not publish specific rate limits for the Dutchie Plus GraphQL API. As an enterprise, per-retailer API, throttling is applied at Dutchie's discretion per API key and is expected to protect the shared ecommerce backend. GraphQL requests are HTTPS POST operations to https://plus.dutchie.com/plus/2021-07/graphql; clients should expect standard HTTP 429 responses when throttled and should cache menu reads and back off on checkout mutations. Specific numeric limits are not documented publicly and are not reconciled in this artifact.

Dutchie Rate Limits is the machine-readable rate-limit profile for Dutchie on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and query_cost.

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

Tagged areas include Cannabis, Dispensary, Ecommerce, GraphQL, and Rate Limiting.

2 Limits Throttle: 429
CannabisDispensaryEcommerceGraphQLRate LimitingQuotasThrottling

Limits

Requests Per Key api_key
requests
see provider documentation
Per-retailer API key throttling applied at Dutchie's discretion; specific RPM/RPS values are not published.
GraphQL Query Complexity api_key
query_cost
see provider documentation
GraphQL APIs commonly enforce query depth/complexity limits; Dutchie does not publish specific thresholds.

Policies

Caching
Cache retailer menu and specials reads client-side / at the edge to reduce request volume against the shared ecommerce backend.
Backoff Strategy
Implement exponential backoff with jitter on HTTP 429 and avoid rapid repeat checkout mutations.

Sources