MyChurchDocs

Changelog

What changed in the API and the integrations it offers, newest first. The rules for what may change are in Versioning.

New platform and these docs

November 2026

  • The developer docs launch at docs.mychurch.co.ke, covering the member app API, the platform API, giving, USSD, biometric devices and SMS.
  • The platform API (/v1, /auth, /webhooks) is available to portal users and to integrations with an mc_ token. It reaches 1.0.0 at the first production release; until then it may still change.
  • New callback paths under /webhooks/mpesa/ for registrations made after the move. Existing registrations keep their URLs.

Member app API: behaviour fixes on the frozen surface

November 2026

  • Payments are credited only after Safaricom confirms them with a Transaction Status query; previously the confirmation alone credited the account. A member sees the receipt SMS a few seconds later than before.
  • The C2B validation URL, the STK result URL and the Transaction Status timeout URL now answer. They were registered but returned errors.
  • Routes with {church} in the path and a member token refuse a token from a different church with HTTP 401.
  • GET /api/v2/today-services on a day with no services returns {"services": []} instead of HTTP 500.
  • OTP codes expire after five minutes and work once. They stay four digits, matching the app.
  • Merchandise orders, fundraiser contributions and fundraiser pledge edits are limited to the member's own church; editing a fundraiser pledge requires the pledging member's token.
  • An event fee already covered by money held for the member is marked paid without sending a zero-amount payment prompt.
  • Mobile Sasa delivery reports mark failed messages as failed, not only delivered ones as delivered.
  • USSD sessions keep their values per session and expire after ten minutes of silence; every reply starts with CON or END.
  • POST /api/v2/export/contributions answers status: false with an upgrade message until PDF statements return.