Funeralone Rate Limits
funeralOne does not publish numeric rate limits for the partner Cases API. The API is partner-gated - access is provisioned per integration partner with an API key and per-customer AccountExternalId associations - so throughput is governed by the partner agreement and funeralOne's certification/test process rather than a public per-minute request cap. In practice, case create/update traffic is low-volume and event-driven (one write per At-Need case and subsequent edits) rather than high-frequency.
Funeralone Rate Limits is the machine-readable rate-limit profile for funeralOne on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests and cases.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Funeral Homes, Deathcare, Partner API, Rate Limiting, and Quotas.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/funeralone-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.