Luma Health · Rate Limits
Luma Health Rate Limits
Luma Health Rate Limits is the rate-limit profile for Luma Health on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the documented and note response headers.
Tagged areas include Healthcare, United States, Patient Engagement, Scheduling, and Referrals.
0 Limits
documentednote
Transcribed from the provider's documentation on 2026-08-15 — apidocs.lumahealth.io (Redoc) + the published spec apidoc....
View Source
Limits
Luma Health publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Luma Health documents NO rate limits for the Rest-Service v2 API. The published OpenAPI (278 operations) declares no 429 response on any operation - the full response-code census is 200 (244), 401 (270), 403 (269), 201 (39), 404 (34), 500 (28), 400 (19), 406/409/422/204 (1 each) - and the strings "rate limit", "ratelimit", "throttle" (as a client contract), "Retry-After" and "X-RateLimit" do not occur anywhere in the document. The only "throttling" in the spec is a BroadcastFlow send-pacing SETTING for mass patient communications, not a client request budget. There is no developer portal beyond the Redoc render and no public help-center article on API limits (support.lumahealth.io serves HTTP 403 to non-browser clients), so no runtime backoff signal is discoverable. An integrator cannot tell from the public surface how many calls per second a Luma tenant may make, nor what the API returns when they exceed it. Limits, if any, are enforced server-side and communicated under contract.
HealthcareUnited StatesPatient EngagementSchedulingReferralsIntakeMessagingEligibilityElectronic Health RecordsInteroperabilityClinical AIReputation ManagementPatient Feedback
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.