3PL Warehouse Manager · Rate Limits

3Plcentral Rate Limits

3PL Warehouse Manager (SecureWMS) does not publish fixed numeric per-minute or per-day request-rate limits for its REST API. The primary documented control is token lifetime: access tokens issued by https://secure-wms.com/AuthServer/api/Token are short-lived (typically valid 30-60 minutes) and Extensiv recommends refreshing the token no less than every 30 minutes and re-requesting on expiry. Collection reads are governed practically by pagination (pgnum/pgsiz, commonly 100-200 records per page) and by RQL filters that scope result sets rather than by a global request cap. All traffic must be HTTPS; plain HTTP is rejected.

3Plcentral Rate Limits is the machine-readable rate-limit profile for 3PL Warehouse Manager 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 4 backoff/retry policies defined and response codes documented for throttled.

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

3 Limits Throttle: 429
Warehouse ManagementWMS3PLLogisticsRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the SecureWMS REST API.
Access Token Lifetime token
minutes
~30-60 minutes
Tokens are short-lived; refresh no less than every 30 minutes and on expiry.
Collection Page Size request
records
pgsiz (commonly 100-200)
List endpoints are paged via pgnum/pgsiz; large pulls loop pages.

Policies

HTTPS Only
All integration traffic must use HTTPS; plain HTTP is not supported.
Token Reuse
Reuse a valid bearer token across requests within its lifetime rather than requesting a new token per call.
Pagination and Filtering
Use pgnum/pgsiz pagination and RQL filters to scope result sets and avoid unnecessary large scans.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources