GET /v1/patients/me/onboarding
Service: patient-graph · operationId: (none)
Returns onboarding state for the authenticated user. Used by the app’s redirect helper to decide whether to send a new member to /onboarding or /today.
Required scopes
(no scope declared — review service config)
Responses
200 Onboarding state
{
"type": "object",
"properties": {
"patient_id": {
"type": "string"
},
"goals": {
"type": "array",
"items": {
"type": "string"
}
},
"role": {
"type": "string",
"enum": [
"patient",
"coach",
"researcher"
]
},
"default_follows": {
"type": "array",
"items": {
"type": "string"
}
},
"notifications": {
"type": "object",
"properties": {
"pushOptIn": {
"type": "boolean"
},
"emailFrequency": {
"type": "string",
"enum": [
"daily",
"weekly",
"off"
]
}
}
},
"onboarding_completed_at": {
"type": [
"string",
"null"
]
}
},
"required": [
"patient_id",
"goals",
"role",
"default_follows",
"notifications",
"onboarding_completed_at"
]
}404 Patient not found for current user
{
"type": "object",
"properties": {
"error": {
"type": "string"
},
"message": {
"type": "string"
}
},
"required": [
"error",
"message"
]
}Example
curl -X GET https://patient-graph.platform.loop.health/v1/patients/me/onboarding \
-H "Authorization: Bearer $ACCESS_TOKEN"Related
services/patient-graph— service overview- All endpoints — directory across services
- Auth model — how scopes are enforced