Skip to main content
GET
Get result detail (wellbeing outcome summaries and artifacts)
Returns the partner-safe result envelope: pipeline status, one or more wellbeing outcomes, and artifacts with signed download URLs when available.

Key response fields

Example request

Example response

See Outcomes model for field interpretation.

Authorizations

X-Api-Key
string
header
required

Plaintext API key issued for the tenant (stored hashed server-side).

Headers

x-request-id
string

Optional; echoed when possible. Server generates when absent.

Path Parameters

resultId
string<uuid>
required

Response

Result scoped to tenant; partner scoping follows submission metadata

Partner GET /v1/results/:id. Minimal fields: ids, submission status, completion time, public outcome summary(ies), and artifact download handles. Multi-outcome runs include outcomes (array, same order as stored inference bundle); outcome remains the primary (first) row for backward compatibility. Omits internal job ids, subject linkage, model metadata, and citation placeholders.

resultId
string<uuid>
required
submissionId
string<uuid>
required
partnerSubmissionId
string | null
required
status
enum<string>
required

Stable public slug for submission pipeline state (partner JSON).

Available options:
received,
validating,
validated,
processing,
completed,
failed,
rejected
statusLabel
string
required
Minimum string length: 1
completedAt
string<date-time>
required

Wall time when the result row was last updated (completion / refresh).

outcome
null | object
required

The primary (first) outcome; null when not yet available.

artifacts
object
required
outcomes
object[]

Included when more than one wellbeing outcome was scored. Order matches the persisted multi-outcome bundle. Omitted for single-outcome results (use outcome only).