GET /v1/sessions/\{id\}/questions
Service: live · operationId: (none)
List session questions, optionally filtered by status, sorted by ‘top’ (votes) or ‘new’.
Required scopes
(no scope declared — review service config)
Path parameters
id(string) required —
Query parameters
status(string) —sort(string) —
Responses
200 Questions
{
"type": "object",
"properties": {
"questions": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"format": "uuid"
},
"session_id": {
"type": "string",
"format": "uuid"
},
"asker_user_id": {
"type": "string"
},
"body": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
"pending",
"approved",
"dismissed",
"answered"
]
},
"vote_count": {
"type": "integer",
"minimum": 0
},
"asked_at": {
"type": "string",
"format": "date-time"
},
"moderated_at": {
"type": [
"string",
"null"
],
"format": "date-time"
},
"moderator_user_id": {
"type": [
"string",
"null"
]
}
},
"required": [
"id",
"session_id",
"asker_user_id",
"body",
"status",
"vote_count",
"asked_at",
"moderated_at",
"moderator_user_id"
]
}
}
},
"required": [
"questions"
]
}Example
curl -X GET https://live.platform.loop.health/v1/sessions/{id}/questions \
-H "Authorization: Bearer $ACCESS_TOKEN"Related
services/live— service overview- All endpoints — directory across services
- Auth model — how scopes are enforced