Connect a church app | Ediphai API

Use the Ediphai API to send records from an app your church runs. Version 1 provides a shared path for keys, definitions, records, receipts, identity, retries and deletion. Each record type has its own body contract and version; assessment results are the only type accepted today. Forms and other types can join version 1 without changing an existing sender’s assessment contract.

Quickstart

Create a test key and send a valid record using the currently supported assessment type.

Supported record types

Check the exact type names, versions and body schemas the API accepts.

Build with a coding agent

Give an agent the current contract and a test workflow for your app.

Delivery and retries

Store requests, handle receipts and recover after uncertain outcomes.

API reference

Inspect endpoints, request fields and response schemas.

Test your sender

Check the eight request and recovery cases before using a live key.

How an integration works

Create a test key in Ediphai Console. It identifies the church, app and environment; keep it on your server.
Declare the definition required by the chosen record type, then send a record with a stable ID and revision.
Save the receipt and check status or reconciliation when delivery is uncertain. Ediphai may hold a record for identity review.
Run the sender self-test before using a separate live key. Test records are validated but do not enter the church’s data.

The API accepts writes, status checks, reconciliation and deletion. It does not let an app read a person’s Ediphai profile or results back out. The OpenAPI file and JSON Schemas are the machine contract; use them for code generation and validation.