POST /v1/admin/inbox/screening-status
Service: comms · operationId: (none)
Required scopes
(no scope declared — review service config)
Request body
{
"type": "object",
"properties": {
"person_id": {
"type": "string",
"minLength": 1
},
"brand_id": {
"type": "string",
"minLength": 1
},
"action": {
"type": "string",
"enum": [
"get",
"seed",
"update"
]
},
"status": {
"type": "string"
}
},
"required": [
"person_id",
"brand_id",
"action"
]
}Responses
200 Screening status result
{
"type": "object",
"properties": {
"person_id": {
"type": "string"
},
"brand_id": {
"type": "string"
},
"status": {
"type": [
"string",
"null"
]
},
"updated": {
"type": "boolean"
}
},
"required": [
"person_id",
"brand_id",
"status",
"updated"
]
}400 Invalid request
{
"type": "object",
"properties": {
"error": {
"type": "string"
},
"message": {
"type": "string"
}
},
"required": [
"error",
"message"
]
}422 Missing required status for update action
{
"type": "object",
"properties": {
"error": {
"type": "string"
},
"message": {
"type": "string"
}
},
"required": [
"error",
"message"
]
}Example
curl -X POST https://comms.platform.loop.health/v1/admin/inbox/screening-status \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ ... }'Related
services/comms— service overview- All endpoints — directory across services
- Auth model — how scopes are enforced