Extensiv · Rate Limits

Extensiv Rate Limits

Extensiv does not publish fixed numeric per-minute request limits for the 3PL Warehouse Manager REST API in its public help documentation. The primary documented throttling control is the access token lifetime: tokens minted at secure-wms.com/AuthServer are short-lived (typically valid 30-60 minutes), so clients must cache and refresh tokens rather than requesting a new token per call. The API is HTTPS-only and paginated (page size / page number), so bulk reads of orders and inventory are expected to page rather than pull everything at once. Any per-account request ceilings are governed by contract and are not published.

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

It captures 3 rate-limit definitions, measuring requests, minutes, and records.

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

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

3 Limits Throttle: 429
3PLWarehouse ManagementWMSRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the 3PL Warehouse Manager REST API.
Access Token Lifetime token
minutes
30-60 minutes (typical)
Tokens expire; cache and refresh rather than minting per request.
Collection Pagination request
records
configurable via page size (pgsiz) / page number (pgnum)
List endpoints return paged HAL collections; page through large result sets.

Policies

HTTPS Only
The API rejects plain HTTP; all traffic must use HTTPS.
Token Reuse
Reuse the bearer token until it nears expiry instead of authenticating on every call.
Backoff Strategy
On 429 or transient 5xx, implement exponential backoff with jitter and honor Retry-After if present.

Sources