Terminal · Rate Limits

Terminal Shop Rate Limits

The Terminal Shop API does not publish explicit numeric rate limits in its developer documentation. Access is authenticated per account via Bearer personal access tokens or OAuth, and standard abuse-prevention throttling applies. Callers should treat HTTP 429 as a throttling signal, honor any Retry-After header, and back off. Per-account or per-token limits are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests.

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

Tagged areas include Coffee, E-Commerce, Developer, SSH, and Ordering.

2 Limits Throttle: 429
CoffeeE-CommerceDeveloperSSHOrderingRate LimitingQuotasThrottling

Limits

Per-Account Requests account
requests
see provider documentation
No numeric per-account request limit is documented publicly.
Per-Token Requests token
requests
see provider documentation
Personal access tokens authenticate calls; no documented per-token quota.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on 429 and 5xx responses and honor Retry-After. Official SDKs retry transient errors automatically.
Sandbox Isolation
Use the dev sandbox (https://api.dev.terminal.shop) for testing so load testing and retries do not place real coffee orders.

Sources