Skip to main content
GET
/
v1
/
user
Get Current User
curl --request GET \
  --url https://api.thefaithapp.com/v1/user \
  --header 'Authorization: Bearer <token>' \
  --header 'X-API-Key: <x-api-key>'
{
  "status": "<string>",
  "data": {},
  "data.uuid": "<string>",
  "data.client": {}
}

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.

Returns the authenticated member profile together with their active church context.

​
Request inputs

​
X-API-Key
string
required
Your client API key from the dashboard (Settings page).

​
Response fields

​
status
string
required
Indicates whether the member lookup completed successfully.
​
data
object
required
The authenticated member record returned from the API.
​
data.uuid
string
The Firebase user identifier linked to this member record.
​
data.client
object
The active church context currently attached to the member.

​
Example response

{
  "status": "Success",
  "data": {
    "id": 1,
    "name": "Jane Doe",
    "email": "jane@example.com",
    "uuid": "firebase-user-123",
    "phone": null,
    "client": {
      "id": 12,
      "public_uuid": "11111111-2222-3333-4444-555555555555",
      "name": "Example Church",
      "timezone": "UTC",
      "date_format": "Y-m-d",
      "time_format": "H:i:s",
      "image": "https://cdn.example.com/clients/example.png"
    }
  }
}
The real response includes additional member and client fields. Sensitive values should not be stored client-side.