Tribute Technology · Rate Limits

Tributetech Rate Limits

The Tribute Store API documentation does not publish fixed numeric rate limits. Access is instead gated up front: an integrator's requests originate from an IP-allowlisted server, are authenticated per funeral home with a short-lived HTML bearer token (expires_in seconds), and are scoped so that only entities created for that funeral home's HostName are visible. The documentation states usage expectations rather than a per-minute cap: partners should push a serving location or obituary update only when the underlying information has actually changed, and should not re-POST on every internal save when nothing in the API contract changed.

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

It captures 4 rate-limit definitions, measuring requests, source-ip, seconds, and writes.

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

Tagged areas include Funeral Technology, Obituaries, Rate Limiting, Quotas, and Partner API.

4 Limits
Funeral TechnologyObituariesRate LimitingQuotasPartner API

Limits

Request Rate partner
requests
not published
No fixed numeric request-rate limit is documented for the Tribute Store API.
IP Allowlist provider
source-ip
allowlisted only
Requests must originate from an IP added to the Provider's allowlist.
Token Lifetime funeral-home
seconds
expires_in (per token response)
The bearer token is valid only for the number of seconds returned by POST /token/.
Update Frequency resource
writes
on-change only
Documentation asks partners to POST location/obituary updates only when the data actually changes.

Policies

Push On Change Only
Do not push obituary or serving-location updates when the information is not changing (for example, on every internal save).
Token Refresh
Re-request a bearer token from POST /token/ when the current token's expires_in window elapses.
Scoped Visibility
A token only exposes entities created for its associated funeral home HostName.

Sources