Particle Health · Rate Limits

Particle Health Rate Limits

Machine-readable rate limit definitions for the Particle Health API. Particle configures limits on a per-project basis with a documented default of approximately 50 queries per minute per project. Multi-project customers receive separate limits per project. Particle reserves the right to apply additional limits to any API. When a client exceeds a limit the API returns HTTP 429 and the client is expected to back off and retry after roughly 60 seconds.

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

It captures 4 rate-limit definitions, across the sandbox, production, and enterprise tiers, measuring requests_per_minute and requests_per_day.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Carequality, CommonWell, FHIR, Health Data, and HIE.

4 Limits Throttle: 429 Quota: 429
CarequalityCommonWellFHIRHealth DataHIEInteroperabilityPatientsQHINTEFCARate LimitingQuotasThrottling

Limits

Sandbox Default Rate Limit project
requests_per_minute · minute
50
Sandbox environment limit; aligns with the documented per-project default.
Sandbox Daily Organization Cap organization
requests_per_day · day
500
Documented, confirmed cap (not an example): "we limit the number of queries within our Sandbox environment to 500 queries per organization per day" — https://sandbox.particlehealth.com, per docs.particlehealth.com/docs/test-patient-sandbox.
Production Default Per-Project Rate Limit project
requests_per_minute · minute
50
Documented baseline of 50 queries per minute per project. Customers with multiple projects stack separately (e.g., 3 projects yields 150 queries per minute aggregate).
Enterprise Negotiated Rate Limit contract
requests_per_minute · minute
500
Negotiated ceiling for enterprise customers; actual value is set in the commercial agreement.

Policies

HTTP 429 Backoff
On a 429 response, clients should wait approximately 60 seconds before retrying since rate limits are tracked per minute. Particle recommends implementing exponential backoff with jitter.
Per-Project Scoping
Rate limits are configured per project. Customers with multiple projects benefit from separate independent limits.
Reservation Clause
Particle reserves the right to implement rate limits on all APIs. Current scope may expand and customers should monitor for 429 responses across all endpoints.
Limit Increases
Customers requiring higher limits should contact their Particle Health success team to negotiate a project-specific increase.
Fair Use
Even on uncapped enterprise tiers, sustained patterns that materially impact shared infrastructure may be subject to fair-use throttling.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/particle-health-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.