Hopstack · Rate Limits

Hopstack Rate Limits

Hopstack does not publish numeric rate limits for its REST API in open materials. The API is gated behind a per-user X-API-Key that Hopstack Support must enable, and quotas or throttling (if any) are governed by the customer's commercial agreement rather than a published per-minute request cap. Any documented limits, throttling response codes, and retry guidance live in the account/partner API reference at apidocs.hopstack.io, which is not openly scrapeable.

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

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

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

Tagged areas include Warehouse Management, WMS, Fulfillment, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Warehouse ManagementWMSFulfillmentRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented in open materials; governed by the customer agreement.
API Key Access account
enablement
gated
API-key generation must be enabled by Hopstack Support before any API calls are possible.

Policies

API Key Security
Keys are shown once at creation and must be stored securely (environment variables); do not share outside the calling microservice.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources