funeralOne · Rate Limits

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.

2 Limits Throttle: 429
Funeral HomesDeathcarePartner APIRate LimitingQuotas

Limits

Cases API Requests partner
requests
not published
No fixed numeric request-rate limit is documented for the partner Cases API.
Per-Customer Scope account
cases
governed by partner agreement
Access is scoped per AccountExternalId associated with the partner's API key.

Policies

Partner Provisioning
Access requires a funeralOne-issued API key and per-customer AccountExternalId associations, established during partner onboarding.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.

Sources