Agave · Rate Limits

Agave Rate Limits

Agave does not publish numeric rate limits for its Unified Construction API on its public site. Limits and throttling behavior are defined per contract, and downstream sync throughput is generally bounded by each integrated source ERP's own rate limits (Procore, Sage, Viewpoint, etc.) rather than Agave-imposed ceilings. Implementation guidance is provided during 1:1 onboarding.

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

It captures 1 rate-limit definition, measuring varies.

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

Tagged areas include Accounting, Construction, Integration, and Rate Limiting.

1 Limits Throttle: 429
AccountingConstructionIntegrationRate Limiting

Limits

Source-system passthrough account
varies
bounded by underlying ERP/source-system rate limits
Agave proxies calls to integrated platforms; effective throughput is typically constrained by the source ERP's published limits rather than an Agave-imposed cap.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on 429 and 503 responses, honoring any Retry-After header returned.
Source-System Pacing
When syncing against rate-limited ERPs (Procore, Sage Intacct, etc.), pace calls to stay within the source platform's published limits even when Agave does not throttle.
Contractual Limits
Throughput, burst, and concurrency expectations are negotiated as part of the customer contract; contact your Agave implementation expert to raise limits.

Sources