Bentley Systems · Rate Limits

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.

5 Limits Throttle: 429
Rate LimitingiTwinThrottling

Limits

Default request throttling client
requests_per_second · second
unspecified
Credit consumption (billing-tied) subscription
credits · month
tier-based
Long-running job queue subscription
concurrent_jobs · continuous
unspecified
Webhook delivery retries subscription
retries · per_event
5
OAuth token lifetime client
seconds · token_lifetime
3600

Policies

Retry on 429
Honor the Retry-After header. Implement exponential backoff with jitter when no header is present.
Correlation IDs
Bentley returns X-Correlation-Id on responses. Capture this for support tickets when reporting throttling, errors, or job failures.
Credit-based capacity
Plan service consumption around your credit allowance rather than around per-second limits. Bulk operations (iModel ingress, reality data ingest, visualization-hours, reporting rows) directly consume credits.
Long-running jobs poll
For asynchronous endpoints (jobs/{id}/progress) poll on the cadence published in the operation documentation; avoid sub-second polling.
Live vs evaluation
Community tier is non-commercial and may receive lower priority in shared job queues than Standard, Premium, and Enterprise tiers.

Sources