funeralOne f1Connect API

Name: funeralOne f1Connect API API
Brand: funeralOne f1Connect API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementbasic3 EndpointsREST

For Agents

Create funeral case records in the funeralOne f1Connect platform and retrieve them by account or case external ID for syncing case management systems with tribute websites.

Connect the funeralOne f1Connect API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the funeralOne f1Connect API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with funeralOne f1Connect API API.

Create a new funeral case with deceased details, events, and serving locations

List all cases under a funeral home account by external account ID

Retrieve a single case by external account and external case identifier

Sync case data from a funeral home management system into f1Connect

GET STARTED

Start building with funeralOne f1Connect API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for funeralOne f1Connect API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for funeralOne f1Connect API, keeping it validated and agent-ready. funeralOne's f1Connect is the integration surface used by funeral homes to sync case records — including details about the deceased, services and events, and serving locations — into the f1Connect platform that powers tribute websites, memorial pages, and family communications. The 3-endpoint API is intentionally small: create a case, fetch all cases for an account, or fetch a single case by external ID, using basic authentication.

Use Cases

Patterns agents use funeralOne f1Connect API API for, with concrete tasks.

★ Funeral Home Case Sync

Sync newly created case records from a funeral home's primary management system into f1Connect so the tribute website, obituary, and family-facing pages are populated automatically. POST /cases creates the record with deceased, event, and serving-location details, and the GET endpoints let the source system reconcile what is already in f1Connect by external ID.

POST /cases with the AccountExternalId, CaseExternalId, deceased details, and event list to create the case in f1Connect

Tribute Website Population

Power a funeral home's tribute website by creating cases through the API as soon as arrangements are entered into the back-office system. The case payload carries the events (visitation, service, committal) and serving locations needed to render the public memorial page without manual entry by the funeral director.

POST /cases for a newly arranged service, then verify creation with GET /cases/AccountExternalId/{AccountExternalId}/CaseExternalId/{CaseExternalId}

Reconciliation Audits

Audit which cases have been pushed into f1Connect for a given funeral home over a period. GET /cases/AccountExternalId/{AccountExternalId} returns all cases for the account, which can be diffed against the source system to catch missed syncs and re-push them. Useful before annual reviews or when changing back-office systems.

GET /cases/AccountExternalId/{AccountExternalId} to enumerate all cases on f1Connect, then diff against the source system list and POST /cases for any missing

AI Agent Case Creation via Jentic

An AI agent that watches the funeral home's case management system can call f1Connect through Jentic to push new cases as they are arranged. Jentic isolates the basic auth credentials and exposes the three operations as discoverable tools, so the agent only needs the case payload.

Search Jentic for 'create a funeral case in f1connect', load the POST /cases schema, and execute with AccountExternalId and the case payload

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for funeralone f1connect api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/cases

Create a funeral case with deceased details, events, and serving locations

GET

/cases/AccountExternalId/{AccountExternalId}

List all cases for a funeral home account

GET

/cases/AccountExternalId/{AccountExternalId}/CaseExternalId/{CaseExternalId}

Retrieve a specific case by external IDs

POST

/cases

Create a funeral case with deceased details, events, and serving locations

GET

/cases/AccountExternalId/{AccountExternalId}

List all cases for a funeral home account

GET

/cases/AccountExternalId/{AccountExternalId}/CaseExternalId/{CaseExternalId}

Retrieve a specific case by external IDs

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

f1Connect's HTTP Basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped tool access; the username/password pair is never exposed to the agent.

Intent-based discovery

Agents search by intent like 'create a funeral case' and Jentic returns the POST /cases operation with its input schema, so the agent skips the funeralOne docs.

Time to first call

Direct f1Connect integration: half a day to a day for basic auth setup, payload mapping, and reconciliation logic. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot

CRM that funeral homes use for family follow-up and aftercare alongside f1Connect's case data

Use HubSpot alongside f1Connect when the funeral home runs aftercare and grief support workflows that need a generalist CRM, with case IDs synced for reference.

Complementary

Salesforce

Enterprise CRM used by larger funeral home groups for cross-location case and family relationship tracking

Use Salesforce alongside f1Connect when a multi-location funeral home group needs unified family relationship tracking on top of the per-case f1Connect record.

Complementary

Pipedrive

Sales CRM used by pre-need (preplanning) funeral sales teams alongside f1Connect's at-need case records

Use Pipedrive alongside f1Connect when there is a separate pre-need sales pipeline that should not pollute the at-need case records in f1Connect.

FAQs

Specific to using funeralOne f1Connect API API through Jentic.

Why is there no official OpenAPI spec for funeralOne f1Connect API?

funeralOne does not publish an OpenAPI specification publicly. Jentic generates and maintains this spec so that AI agents and developers can call funeralOne f1Connect API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the funeralOne f1Connect API use?

f1Connect uses HTTP Basic authentication with credentials issued by funeralOne. Through Jentic, the credentials are stored in the encrypted vault and the Authorization header is composed at execution time so they never enter the agent's context.

Can I list all cases for a single funeral home account?

Yes. GET /cases/AccountExternalId/{AccountExternalId} returns every case associated with that account's external ID. The response is keyed by CaseExternalId so the source system can reconcile what is already on f1Connect.

How do I create a case with multiple events and serving locations?

POST /cases accepts events and serving locations as nested arrays in the case payload, alongside deceased details. Submit them in a single request rather than chained calls — there is no separate endpoint for adding events to an existing case.

How do I push a new case to f1Connect through Jentic?

Run pip install jentic, then search 'create a funeral case in f1connect'. Jentic returns the POST /cases operation with its input schema. Execute with the AccountExternalId, CaseExternalId, and case payload; Jentic handles the basic auth header.

What identifies a case uniquely in this API?

The combination of AccountExternalId (the funeral home) and CaseExternalId (the case in the source system). Both are provided by the integrating system on POST /cases and reused on the GET endpoints, so f1Connect mirrors the source system's identifiers.