Extended load-balance mechanism for integrations (API throttling)
Clinical One Cloud Service 26.2 introduced API throttling, which is a rate-limiting approach to manage API request volume. As part of this release, API throttling is extended to cover the API categories that were not included in the initial implementation.
API throttling is intended to control high volumes of external API traffic to help maintain consistent Clinical One Cloud Service performance. Extending to the remaining API categories ensures total coverage and provides consistent protection across Clinical One Cloud Service while preserving a steady product behavior.
- Codelist
- Coding
- Comments
- Data Actions
- Designer (including Designer ORS, Designer EDC, and Designer Study)
- File Upload
- Library
- Notifications
- Query
- Reporting
- Rule Designer
- Rule Execution
- Sites and Depots
- Users, Permissions, and Roles
Remember that throttling is only applied to external requests and only if the defined limits are exceeded. So, if the limits for external API requests are surpassed while using integrations, you get a 429 - Too Many Requests error response. This response also provides the details on when to retry the request.
You can find additional information about this error response in the REST API for Clinical One Cloud Service guide, after the assessment environment upgrade completes.
Parent topic: Integrations