Spruce Health · Rate Limits

Spruce Health Rate Limits

Spruce Health publishes no numeric request-rate limit for the Public API, but it does publish the runtime signal, which is the part an agent actually needs. Every response carries rate-limit headers across two windows - 60 seconds and 24 hours - and Spruce documents that limits are enforced PER ORGANIZATION, not per credential, so issuing additional tokens buys no additional headroom. On the webhook delivery side the limit is concrete and published: 1000 events per minute per endpoint.

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

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

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, throttled_note, forbidden, forbidden_note, duplicate, and duplicate_note.

Tagged areas include Healthcare, HIPAA, Communication, Rate Limiting, and Quotas.

3 Limits Throttle: not-documented
HealthcareHIPAACommunicationRate LimitingQuotasWebhooks

Limits

Public API Requests (minute window) organization
requests
not published
The ceiling is not published, but it is discoverable at runtime from the first response an organization receives.
Public API Requests (daily window) organization
requests
not published
Applied "for others" per the overview - the daily dimension does not apply to every request, and its headers are absent on requests it does not govern.
Webhook Delivery Rate endpoint
events
1000
Each registered webhook endpoint is limited to 1000 events per minute. If exceeded, events resume sending after the rate limit window has passed - they are throttled, not dropped.

Policies

Per-organization enforcement
Limits attach to the organization, not the token. Minting extra credentials does not raise the ceiling, and one noisy integration will throttle every other integration in the same practice.
Header-driven backoff
Watch s-ratelimit-remaining and s-ratelimit-daily-remaining and slow down before exhaustion; the exhaustion status is undocumented so it cannot be relied on as the trigger.
Idempotent retry
On a retry of a POST or PATCH, reuse the same s-idempotency-key. Spruce rejects the duplicate with 422 rather than replaying the original response, so a 422 on retry means the first attempt landed.
Webhook signature verification
Endpoints receive a signing secret at creation and should verify the X-Spruce-Signature HMAC-SHA256 value in constant time before acting on an event.

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

GitHub Google LinkedIn

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