Skip to main content
POST
/
v1
/
events
/
{event}
/
register
Register For Event
curl --request POST \
  --url https://api.thefaithapp.com/v1/events/{event}/register \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <x-api-key>' \
  --data '
{
  "registrant_name": "<string>",
  "registrant_email": "<string>",
  "phone": "<string>",
  "guests": 123,
  "notes": "<string>",
  "member_id": 123
}
'
{
  "status": "<string>",
  "message": "<string>",
  "data": {},
  "data.status": "<string>",
  "data.registration_date": "<string>",
  "data.checked_in": true
}

Documentation Index

Fetch the complete documentation index at: https://docs.thefaithapp.com/llms.txt

Use this file to discover all available pages before exploring further.

Creates a built-in event registration for the authenticated member.

Request body

{
  "registrant_name": "Jane Doe",
  "registrant_email": "jane@example.com",
  "phone": "+256700000000",
  "guests": 1,
  "notes": "Looking forward to it",
  "member_id": 1
}

Request inputs

X-API-Key
string
required
Your client API key from the dashboard (Settings page).
event
number
required
Unique identifier of the event to register for.
registrant_name
string
required
Send registrant_name in the JSON body.
registrant_email
string
required
Send registrant_email in the JSON body.
phone
string
Send phone in the JSON body.
guests
number
Send guests in the JSON body.
notes
string
Send notes in the JSON body.
member_id
number
required
Send member_id in the JSON body.

Response fields

status
string
required
Indicates whether the registration request completed successfully.
message
string
required
Human-readable confirmation of the registration outcome.
data
object
required
The stored event registration record returned after creation or update.
data.status
string
The registration state saved for the member, such as registered.
data.registration_date
string
When the registration was recorded by the API.
data.checked_in
boolean
Whether this registration has already been checked in on event day.

Example response

{
  "status": "Success",
  "message": "Registration successful",
  "data": {
    "id": 1,
    "event_id": 131,
    "member_id": 1,
    "name": "Jane Doe",
    "email": "jane@example.com",
    "phone": "+256700000000",
    "guests": 1,
    "notes": "Looking forward to it",
    "status": "registered",
    "registration_date": "2026-05-27T17:57:14.000000Z",
    "checked_in": false,
    "check_in_time": null
  }
}
This endpoint only works for events that use built-in registration.