Teelaunch · Rate Limits

Teelaunch Rate Limits

Teelaunch does not publish fixed numeric rate limits for its public REST API in the OpenAPI document or the API-token knowledge base. Access is gated first by account verification - a new account's API token does not function until the account is verified, which typically completes within 24 hours (up to 72). Beyond that, standard REST throttling conventions should be assumed. Clients should honor 429 responses with exponential backoff and treat the outbound shipment-tracking webhook (configured in Developer Settings) as the push channel rather than polling order/shipment endpoints aggressively.

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

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

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

Tagged areas include Print on Demand, POD, Orders, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Print on DemandPODOrdersRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the public REST API.
Account Verification Gate account
verification
required before API token functions
New accounts must be verified (typically 24h, up to 72h) before the API token works.
Order Submission account
orders
not published
No documented cap on order creation volume; governed by account standing and production capacity.

Policies

Backoff Strategy
On 429 responses, implement exponential backoff with jitter and honor any Retry-After header.
Webhook Over Polling
Use the shipment-tracking webhook configured in Developer Settings to receive fulfillment updates instead of polling the shipments endpoints.

Sources