Waystar · Rate Limits

Waystar Rate Limits

Waystar publishes exactly ONE numeric API limit: ImmediateClaims rejects any submission of more than 50 claims, effective 2019-08-01, with the error "Invalid request. Too many claims." Everything else is undisclosed. There are no per-second, per-minute or per-day request caps published on any surface, no documented concurrency ceiling, and no published quota tied to a plan. Rates and concurrency are set by the client or partner contract and are further bounded by the downstream payer.

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

It captures 7 rate-limit definitions, measuring claims, identical POSTs, failed connections, requests, and concurrent.

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

Tagged areas include Healthcare, Revenue Cycle Management, Clearinghouse, X12 EDI, and Rate Limiting.

7 Limits Throttle: not published
HealthcareRevenue Cycle ManagementClearinghouseX12 EDIRate LimitingQuotas

Limits

ImmediateClaims batch size per-request
claims
50
Estimation duplicate-POST suppression per-signature
identical POSTs
1
SFTP connection attempts per-source-IP
failed connections
5
Real-time API requests account
requests
not published
Real-time eligibility/status/auth transaction rates are contract- and payer-governed; no public numeric cap.
Real-time concurrency account
concurrent
not published
Concurrent real-time transaction limits are provisioned per integration.
Batch / SFTP submission account
files
contract-defined
Batch claim and file exchange volumes and windows are set by the client agreement.
Payer-side availability payer
availability
payer-dependent
Downstream payer maintenance windows and payer timeouts bound effective throughput regardless of any Waystar limit, and surface as "Failed at Payer" or payer-timeout conditions rather than as a throttle.

Policies

Undisclosed request rates
Waystar does not publicly document numeric request-rate limits; they are established per partner/client contract during onboarding.
No runtime throttling signal
Because no rate-limit headers and no 429 are published, a client cannot back off on a signal. Retry logic must be conservative and must not blind-retry claim submission or payment calls, which are not idempotent.
Payer windows
Real-time transactions may be constrained by payer availability windows outside Waystar's control.

Sources

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/waystar-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 email required.

GitHub Google LinkedIn

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