Services, check-ins and visitors

A service is the recurring definition (Sunday first service, 08:00 to 10:00). Each day it runs, the api generates a schedule for that date with its own 4-digit check-in code; check-ins attach to a schedule. Every read route also accepts head_office:churches:view and system:churches:view with an X-Church header.

Services

Read routes accept church:services:view, church:checkins:view or church:sunday_school:view.

# Paste your token once (it starts with mc_):
export MYCHURCH_TOKEN="mc_your_token_here"

curl -X POST https://uat-api.mychurch.co.ke/v1/services \
  -H "Authorization: Bearer $MYCHURCH_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "First Service",
    "type": "permanent",
    "day_of_the_week": "Sunday",
    "from_time": "08:00",
    "to_time": "10:00",
    "send_alert": true,
    "message": "Dear [name], [service_name] at [church_name] starts at [from_time]. Welcome!"
  }'

Check-ins

Members check themselves in from the app or USSD with the day's code, devices check them in by fingerprint, and ushers record anyone else here. Lists are read for a date window (default the current month).

# Paste your token once (it starts with mc_):
export MYCHURCH_TOKEN="mc_your_token_here"

curl -X POST https://uat-api.mychurch.co.ke/v1/checkins \
  -H "Authorization: Bearer $MYCHURCH_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "schedule_uuid": "7a2e9c10-0000-4000-8000-00000000c001",
    "member_uuid": "0b6f4c1e-1111-4a2b-9c3d-000000000001"
  }'

Sunday school

Biometric devices

A device is registered by its serial number and assigned to a schedule; it then posts each scan to the device endpoint and the member is checked in. Biometric devices covers the device side.

{
  "serial_number": "ZK-0000-EXAMPLE-01",
  "name": "Main entrance",
  "location": "Sanctuary, east door"
}

Visitors

First-time guests, their answers to the church's welcome questionnaire, and conversion into members.