Boomi · Rate Limits
Boomi Rate Limits
Boomi does not publish a single global per-second / per-minute rate-limit for its platform REST, SOAP, and GraphQL APIs. Limits are enforced per service (Platform API, API Management gateway, Event Streams, MFT) and are bound to the customer's contracted edition. Consumers should expect HTTP 429 throttling, apply exponential backoff, and consult the service-specific docs for any published per-endpoint ceilings.
6 Limits
Throttle: 429
AI AgentsAutomationB2BData IntegrationEDIIntegrationsManagementMFTPlatformWorkflowsRate Limiting
Limits
Boomi Platform REST API account
see service-specific documentation
Limits vary by edition and endpoint.
Boomi API Management gateway account
configurable per API contract
API Management lets administrators define per-contract throttling on published APIs.
Boomi Event Streams REST API account
see service-specific documentation
Boomi DataHub API account
see service-specific documentation
Boomi MFT API account
see service-specific documentation
Boomi API Gateway GraphQL API account
see service-specific documentation
Policies
Backoff Strategy
Apply exponential backoff with jitter on 429 and 5xx responses; honor Retry-After when present.
Edition-Bound Capacity
Effective request capacity is set by the contracted edition (Professional through Enterprise Plus); upgrade or scale-out is required for higher steady-state throughput.
Configurable Throttling (API Management)
For APIs published through Boomi API Management, throttling policies are administrator-defined per API contract and applied at the gateway layer.
Fair Use
Sustained traffic that materially impacts shared infrastructure is reviewed and may trigger throttling regardless of contract.