SuperChurch API

Developer Access

Bring a church's public information to its own website.

SuperChurch API v1 gives a church-controlled server access to its public profile, approved events, and SuperChurch live page. One key is limited to one church.

Manage API Keys OpenAPI Spec

Keys stay on your server.

Do not place an API key in a public webpage, browser script, mobile app, or source repository. The API does not allow browser CORS.

What you can read

GET /v1/church/profile

Church name, location, denomination, public website, and public page URL.

GET /v1/church/events

Approved events explicitly marked public or churchwide. Private notes and member-only events stay out.

GET /v1/church/live

Whether the church is live and the public SuperChurch viewer link. No stream keys are returned.

Make a request

curl -H "Authorization: Bearer $SUPERCHURCH_API_KEY" \
  "https://us-central1-supermom-c3c3d.cloudfunctions.net/superChurchApiV1/v1/church/profile"

Event requests accept ISO dates with from and to, a page size up to 100, and a returned cursor for the next page. The date range is limited to 366 days.

Manage access

A church admin or pastor can create and revoke keys in Pastor Portal → API. Choose only the read permissions a service needs. Keys expire after 30, 90, 180, or 365 days; each church can have ten active keys. A removed church manager's keys stop working.

Private church work stays private

Version 1 does not expose members, contact lists, messages, care requests, attendance, giving records, internal notes, invite links, or streaming credentials. It is read-only and runs on SuperChurch's existing Firebase project. Normal Google Cloud usage charges may apply.