Gelato · Rate Limits

Gelato Rate Limits

The Gelato API is authenticated per account with an X-API-KEY and is served over HTTPS across the order, product, shipment, and ecommerce subdomains. Gelato applies request throttling to protect its platform, but specific per-endpoint request-per-minute or per-day limits are not published in the public API documentation and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests.

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

Tagged areas include Print on Demand, Ecommerce, Fulfillment, Distributed Production, and Rate Limiting.

4 Limits Throttle: 429
Print on DemandEcommerceFulfillmentDistributed ProductionRate LimitingQuotasThrottling

Limits

Per-Account Requests account
requests
see provider documentation
Throttling is applied per API key; numeric thresholds are not publicly documented.
Orders API account
requests
see provider documentation
Applies to order.gelatoapis.com create, search, quote, get, patch, and cancel.
Product Catalog and Prices/Stock API account
requests
see provider documentation
Applies to product.gelatoapis.com catalog, product, prices, and stock endpoints.
Ecommerce API account
requests
see provider documentation
Applies to ecommerce.gelatoapis.com store product and template endpoints.

Policies

HTTPS Required
All API requests must be made over HTTPS; plain HTTP calls fail.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources