Sage X3 · Rate Limits
Sage X3 Rate Limits
Sage X3 does not publish specific, universal rate limits for its REST or GraphQL web services. Practical limits are determined by deployment type (cloud vs. on-premise), server capacity, and contract terms. The following entries reflect known guidance from Sage developer documentation and community resources.
Sage X3 Rate Limits is the machine-readable rate-limit profile for Sage X3 on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions.
Tagged areas include ERP, Enterprise Resource Planning, Manufacturing, Distribution, and Supply Chain.
3 Limits
ERPEnterprise Resource PlanningManufacturingDistributionSupply ChainFinancialsAccountingInventoryMid-MarketEnterprise
Limits
REST Web Services (Cloud / SaaS)
Sage X3 Online (SaaS) does not publicly document specific request-per-minute or daily call quotas for REST web services. Limits are enforced server-side and may vary by contract. Exceeding undisclosed thresholds may result in HTTP 429 Too Many Requests responses. Customers should contact Sage support to obtain the limits applicable to their subscription.
GraphQL API (Cloud and On-Premise)
The GraphQL endpoint does not have publicly documented rate limits. GraphQL queries should be optimized to avoid deeply nested or overly broad queries which can place excessive load on the server. Use pagination (first / after) to limit result set sizes.
On-Premise REST / SOAP Web Services
For on-premise deployments, effective rate limits are determined by the customer's own hardware resources (CPU, memory, Sage X3 Syracuse server capacity). Sage recommends implementing retry logic with exponential back-off and avoiding bursts of concurrent requests to the Syracuse node.