Gooten · Rate Limits

Gooten Rate Limits

Gooten does not publish fixed numeric rate limits for its REST API. Access is keyed to your RecipeID and, for order and billing operations, your PartnerBillingKey. Catalog reads (products, variants, templates, countries, currencies) support pagination via page and pageSize parameters and an optional compression flag to reduce payload size, which are the primary tools for managing large catalog pulls. Order submission is naturally bounded by real production. No per-minute or per-day request cap is documented as of the review date.

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

It captures 3 rate-limit definitions, measuring requests, items, and orders.

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

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

3 Limits Throttle: 429
Print on DemandFulfillmentEcommerceRate LimitingQuotas

Limits

API Requests recipe
requests
not published
No fixed numeric request-rate limit is documented for the Gooten API.
Catalog Pagination request
items
configurable via page and pageSize
Product and variant listings are paginated; use compression=true to reduce payload size.
Order Submission recipe
orders
not published
Bounded by real manufacturing; no documented cap on order POSTs.

Policies

HTTPS Required
All requests must use HTTPS; plain HTTP calls fail.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.
Idempotency
Set IsPartnerSourceIdUnique with a stable SourceId on order submission to avoid duplicate orders on retry.

Sources