Bentley Systems Rate Limits
Bentley does not publish granular per-API rate limits on the iTwin Platform developer portal. Throttling is governed at runtime through HTTP 429 responses with Retry-After hints and through the credit metering model that limits service consumption per billing period. Long-running jobs (Reality Modeling, Synchronization, Transformations, Reality Analysis) are queued and progress must be polled via /progress endpoints rather than rate-limited per-second.
Bentley Systems Rate Limits is the machine-readable rate-limit profile for Bentley Systems on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests_per_second, credits, concurrent_jobs, retries, and seconds.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, unauthorized, forbidden, and notFound.
Tagged areas include Rate Limiting, iTwin, and Throttling.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.