Current Church API
Planned external contract for resolving the church attached to an Amen API key.
This endpoint resolves the church attached to the caller’s Amen credential. The tenant is a Core workspace presented as a church in the Forms product.
Delivery status
The browser route exists at GET /api/v1/me, but currently returns
501 AMEN_RESOURCE_GATEWAY_UNAVAILABLE. Core already owns API-key lifecycle and workspace
data; the missing piece is the external resource gateway that validates a Core key and
forwards a tenant-scoped request.
Required contract
GET /api/v1/me
x-api-key: YOUR_AMEN_API_KEY{
"church": {
"id": "workspace_uuid",
"name": "Saint-Paul",
"slug": "saint-paul"
}
}The gateway must derive the workspace from the credential. A caller must never provide a workspace id that can override the key’s tenant.
Amen ownership
- Identity authenticates interactive people and OAuth clients.
- Core owns the workspace and API key.
- The Forms resource gateway exposes the stable public representation.
Until that gateway is implemented, examples that pretend this endpoint succeeds would be
misleading, so the 501 response is intentional.
Amen Forms