funeralOne

funeralOne is a funeral-home technology company whose f1Connect platform delivers funeral-home websites, memorial/tribute pages, Life Tributes tribute videos, memorial webcasting, and e-commerce for independent funeral homes. funeralOne publishes a partner integration API (base https://api.funeralone.com) that lets funeral-management / case-management systems push deceased, obituary, service-event, tribute-video, and family-administration data into a funeral home's f1Connect account so an At-Need case automatically populates the memorial website and Life Tributes. The API is partner-gated - access requires an API key issued by a funeralOne engineer and per-customer AccountExternalId associations - and uses HTTP Basic authentication. Only the Cases resource is publicly documented; the broader website, e-commerce, and webcasting products are delivered through the f1Connect platform rather than a public API.

funeralOne publishes 1 API on the APIs.io network: Cases API. Tagged areas include Funeral Homes, Deathcare, Obituaries, Tribute Videos, and Memorial Websites.

funeralOne’s developer surface includes authentication, documentation, support, and 7 more developer resources.

🌐 Visit website 📡 Source on GitHub

38.2/100 thin ▬ flat Agent 31/100 agent aware Full breakdown ↓
scored 2026-08-03 · rubric v0.9

AccessPaidSelf serve

1 APIs

Funeral HomesDeathcareObituariesTribute VideosMemorial WebsitesLife TributesCase ManagementPartner API

Kin Score

Kin Score How this is scored →
scored 2026-08-03 · rubric v0.9

Composite quality — 38.2/100 · thin

Contract Quality 15.9 / 25

Developer Ergonomics 4.8 / 20

Commercial Clarity 7.9 / 20

Operational Transparency 2.7 / 13

Governance 0.0 / 12

Discoverability 6.9 / 10

Agent readiness — 31/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/funeralone: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

funeralOne Cases API

Create, update, and retrieve funeral cases (obituaries) for an account.

Pricing Plans 1

Published pricing tiers and plan structures.

Funeralone Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Funeralone Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Funeralone Finops

FINOPS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Funeralone Authentication

http · 1 scheme

SECURITY

Funeralone Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Funeralone Agentic Access

3 operations · 1 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 2

The organization behind the API

Website

Website

LinkedIn

Source (apis.yml)

aid: funeralone
url: https://raw.githubusercontent.com/api-evangelist/funeralone/refs/heads/main/apis.yml
name: funeralOne
kind: company
description: funeralOne is a funeral-home technology company whose f1Connect platform delivers funeral-home websites, memorial/tribute
  pages, Life Tributes tribute videos, memorial webcasting, and e-commerce for independent funeral homes. funeralOne publishes
  a partner integration API (base https://api.funeralone.com) that lets funeral-management / case-management systems push
  deceased, obituary, service-event, tribute-video, and family-administration data into a funeral home's f1Connect account
  so an At-Need case automatically populates the memorial website and Life Tributes. The API is partner-gated - access requires
  an API key issued by a funeralOne engineer and per-customer AccountExternalId associations - and uses HTTP Basic authentication.
  Only the Cases resource is publicly documented; the broader website, e-commerce, and webcasting products are delivered through
  the f1Connect platform rather than a public API.
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/funeralone.png
tags:
- Funeral Homes
- Deathcare
- Obituaries
- Tribute Videos
- Memorial Websites
- Life Tributes
- Case Management
- Partner API
created: '2026-07-03'
modified: '2026-07-03'
specificationVersion: '0.19'
apis:
- aid: funeralone:funeralone-cases-api
  name: funeralOne Cases API
  description: Create, update, and retrieve funeral cases (obituaries) for an account.
  humanURL: https://api.funeralone.com/docs/
  baseURL: https://api.funeralone.com
  tags:
  - Cases
  properties:
  - type: OpenAPI
    url: openapi/funeralone-cases-api-openapi.yml
  - type: Documentation
    url: https://api.funeralone.com/docs/
  - type: APIReference
    url: https://api.funeralone.com/docs/
  - type: PostmanCollection
    url: collections/funeralone.postman_collection.json
common:
- type: AgenticAccess
  url: agentic-access/funeralone-agentic-access.yml
- type: DomainSecurity
  url: security/funeralone-domain-security.yml
- type: Authentication
  url: authentication/funeralone-authentication.yml
- type: Website
  url: https://www.funeralone.com
- type: LinkedIn
  url: https://www.linkedin.com/company/funeralone
- type: Documentation
  url: https://api.funeralone.com/docs/
- type: Support
  url: https://support.funeralone.com
- type: Plans
  url: plans/funeralone-plans-pricing.yml
- type: RateLimits
  url: rate-limits/funeralone-rate-limits.yml
- type: FinOps
  url: finops/funeralone-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Where this information came from

This is an independent, third-party profile of funeralOne, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.