MyChurch Developer Documentation

Everything lives on one API at https://api.mychurch.co.ke. It answers two families of routes that look different on purpose:

• The member app API under /api/v2/ (and its older twin /api/v1/) is what the shipped MyChurch apps, Safaricom, the banks, USSD gateways and biometric devices already call. It is frozen: paths, field names and response bodies never change, so an app installed years ago keeps working.
• The platform API under /v1/, with /auth/ for logins, is the modern contract the portal uses. It has real HTTP status codes, a consistent {success, data} envelope, uuids everywhere and permission checks on every route.

The 30-second picture

curl -X POST https://api.mychurch.co.ke/api/v2/login-phone \
  -H "Content-Type: application/json" \
  -d '{"phone": "254712345678"}'

{
  "churches": [
    { "uuid": "00000000-0000-4000-8000-000000000001", "church_name": "Grace Chapel Nairobi" }
  ],
  "message": "Success",
  "status": true
}

That is a real public route on the member app API. The Quickstart goes from here to a logged-in member and their giving history, then does the same on the platform API.

Find your way

• Member App API

  The /api/v2 routes the MyChurch apps call: login, profile, giving, check-ins, groups, events and content.

• Platform API

  The /v1 routes behind the portal, for church systems and integrations: members, groups, services, giving, finance and reports.

• Giving & Payments

  Paybill and till setup, account numbers, STK push, payment verification and bank integrations.

• USSD

  The gateway contract for a church USSD code: five form fields in, CON or END out.

• Biometric devices

  Fingerprint and face devices that check members into services by serial number.

• SMS

  Church SMS through Mobile Sasa: sender IDs, transactional and general messages, delivery reports.

Who these docs are for

• The app team maintaining the MyChurch and white-label apps: start with the Member App API and Authentication.
• Church technical staff connecting a paybill, a bank account, SMS or a check-in device: start with Paybill setup, SMS and Biometric devices.
• Partners (banks, USSD gateways, ERP and CRM systems): see Bank integrations, Callback URLs and USSD.

Money is verified before it moves

A payment notification from Safaricom or a bank is treated as a claim, not as money. MyChurch stores it, confirms it with Safaricom's Transaction Status API, and only then credits the collection account and sends the receipt. Nothing is dropped: a payment that cannot be matched lands in the church's incoming payments list for review. Payment verification explains the whole path.