Updox · Rate Limits

Updox Rate Limits

Updox does not publish fixed numeric per-endpoint rate limits for its public IO API. API access is partner-provisioned and governed by an API Acceptable Use Policy rather than an open, self-serve quota page. In practice, usage is shaped by subscription-tier allowances (monthly caps on faxes, telehealth sessions, appointment reminders, and broadcast messages) rather than by a documented requests-per-minute ceiling. The FaxOemPop / PopPDF retrieval functions are self-throttling by design - they return one fax per call and cap repeated redelivery of an unacknowledged fax at 10 retries until lastRetrievedFaxId is supplied.

Updox Rate Limits is the machine-readable rate-limit profile for Updox on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, retries, and messages.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Healthcare, Secure Messaging, Electronic Fax, Rate Limiting, and Quotas.

3 Limits Throttle: not published
HealthcareSecure MessagingElectronic FaxRate LimitingQuotas

Limits

IO API Requests application
requests
not published
No fixed numeric per-endpoint request-rate limit is documented for the IO API.
Fax Retrieval Redelivery account
retries
10 retries per unacknowledged fax
FaxOemPop/PopPDF re-return the same fax up to 10 times until lastRetrievedFaxId marks it handled.
Subscription Allowances account
messages
per plan
Monthly caps on faxes, telehealth sessions, reminders, and broadcast messages are set by the subscription tier, not by an API rate limit.

Policies

Acceptable Use Policy
API usage is governed by Updox's API Acceptable Use Policy, agreed to during partner onboarding.
Fax Acknowledgement
Clients must supply lastRetrievedFaxId on each poll so retrieved faxes are marked handled and the queue advances toward endOfQueue.
Backoff Strategy
Clients should poll on a reasonable interval and implement exponential backoff with jitter on errors.

Sources