Review quotas and constraints within Redox. Talk to your Technical Account Manager if you have questions about these.
Redox has message and file limits for both incoming and outgoing traffic. If a message exceeds these limits, the message will error.
Type of traffic
Redox API traffic (e.g., Redox Data Model API, Redox FHIR® API, or Redox Platform API)
Carequality Interoperability Framework (for Redox Access™)
HL7v2 messages over MLLP
All other integrations or APIs
To protect you and our other customers, we employ rate limiting across our APIs. You can make up to 10,000 requests every five minutes per user as determined by IP address. Learn about rate limiting.
If your IP address exceeds this limit—until the five-minute window has elapsed—we respond to requests by:
- sending an HTTP 429 status code response (learn about HTTP 429 status), and
- adding an X-RateLimit-Limit HTTP response header with the current limit (7,500).
This limit should be sufficient for any nominal operation, but it may cause issues during backfilling. We expect you to throttle your API requests to stay within this limit. If this isn't possible, submit a ticket via our Help Desk to examine alternative options.