Cherished Book / Developer API

Overview

The Cherished Book API lets funeral homes and memorial-service providers create and manage memorials for the families they serve, at scale. It is a JSON HTTP API; all requests are made over HTTPS to https://app.cherishedbook.com/api/v1.

Every token belongs to one organisation and only ever sees that organisation's data.

Individuals can connect an AI assistant to look after their own memorials, using a personal token from the device flow. If that is what you are here for, the AI assistants page explains it without the technical detail, and the reference in plain Markdown is the version an assistant can read directly.

If you only need to hand someone a part-completed form, and not to create or manage anything yourself, an onboarding link needs no client, no authentication and no integration work.

Authentication

The API uses bearer tokens. Send your token on every request:

curl https://app.cherishedbook.com/api/v1/ping \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/json"

A Business Admin creates a token in Business settings, under API tokens. It is shown once, so copy it then and keep it safe like a password. You can revoke a token at any time from the same screen. If you think a token has been exposed, revoke it there, or contact us and we will help.

Rate limits

Business tokens are limited to 50 requests per minute. Each response includes the standard rate-limit headers; exceeding the limit returns 429 Too Many Requests.

Errors

The API uses conventional HTTP status codes and returns a JSON body on failure:

{
  "message": "The given data was invalid.",
  "errors": { "value": ["The value field is required."] }
}
StatusMeaning
401Missing or invalid token
403Token lacks the required scope
404Resource not found (or out of your scope)
422Validation failed
429Rate limit exceeded

API reference