Skip to Main Content

API, CLI, SDK & Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

"Too Many Requests" Error - Single User API Usage - Need Rate Limit Clarification - FOR CERNER EHR

Ajay MatsagarMay 27 2025

I'm experiencing frequent "Too Many Requests" (HTTP 429) errors when calling Cerner EHR APIs for patient bulk data export, despite being the only user of the API.
**Error Details:** When hitting the Cerner patient bulk data endpoint,
I consistently get:
{
"status": 429,
"response": {
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "throttled",
"diagnostics": "Too Many Requests"
}
]
}
}"

Questions:

  1. What are the exact rate limits for Cerner EHR bulk data export APIs?
  2. How can I monitor my current request rate to understand if I'm hitting limits?
  3. What triggers this throttling - is it requests per second, per minute, or per hour?
  4. Are there different rate limits for bulk data operations vs individual record requests?
  5. Is there a recommended polling interval for bulk data export status checks?

Current Behavior:

  • Getting 429 errors consistently when requesting patient bulk data
  • Only one application making requests
  • Error occurs during initial bulk data request, not status polling
  • Same error format across different attempts

Expected Outcome: Need guidance on proper rate limiting practices for Cerner EHR bulk data operations and how to avoid throttling errors.

Any documentation or best practices for bulk data export rate limits would be greatly appreciated.

Comments
Post Details
Added on May 27 2025
0 comments
113 views