STACK · Rate Limits

Stack Takeoff Rate Limits

STACK does not publish fixed numeric request-rate limits for its REST API v2 in its public developer materials. The documented constraints are OAuth 2.0 token lifetimes rather than per-minute request caps: access tokens are valid for 8 hours, authorization codes for 5 minutes, and refresh tokens for 90 days. Because the API is access-gated (API-Enabled Subscription or partner agreement), any concrete throttles or per-account quotas are established with STACK when credentials are issued and confirmed in the access-controlled API reference.

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

It captures 4 rate-limit definitions, measuring requests and duration.

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

Tagged areas include Construction, Preconstruction, Takeoff, Estimating, and Rate Limiting.

4 Limits Throttle: 429
ConstructionPreconstructionTakeoffEstimatingRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented publicly for STACK API v2.
Access Token Lifetime token
duration
8 hours
OAuth 2.0 access tokens expire after 8 hours; refresh before expiry.
Authorization Code Lifetime token
duration
5 minutes
Three-legged authorization codes are single-use and expire in 5 minutes.
Refresh Token Lifetime token
duration
90 days
Refresh tokens extend user permission verification for up to 90 days.

Policies

Token Caching
Reuse a cached access token for its 8-hour lifetime instead of authenticating on every request.
Backoff Strategy
On 429 or 5xx responses, retry with exponential backoff and jitter and honor any Retry-After header.
Negotiated Limits
Concrete throttles and quotas are set with STACK when API credentials are issued and documented in the access-controlled reference.

Sources