Thrive AI Health
Api reference

Read meal log analysis (async-generated)

Returns the analysis produced after a `PUT` on the meal log. `status` is `processing` while the job is in flight, `ready` when complete, and `failed` if the job errored. While `processing`, `analysis_summary` may be empty — partners typically show a spinner until `status=ready`.

GET
/v1/users/{user_id}/meals/{meal_id}/analysis

Authorization

MemberBearer
AuthorizationBearer <token>

Member-scoped JWT minted by POST /v1/auth/token. Required on every /v1/users/{user_id}/... route; the token's sub claim must match the path user_id.

In: header

Path Parameters

user_id*User Id
Formatuuid
meal_id*Meal Id
Formatuuid

Header Parameters

org-id?string|null
x-user-id?string|null
x-request-id?string|null
traceparent?string|null
Idempotency-Key?|null

Response Body

application/json

application/json

curl -X GET "https://loading/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08/meals/497f6eca-6276-4993-bfeb-53cbbbba6f08/analysis"
{
  "data": {
    "meal_id": "e8f91bba-a1fd-4250-b513-e8e22cf6d4ad",
    "status": "processing",
    "job_id": "453bd7d7-5355-4d6d-a38e-d9e7eb218c3f",
    "analysis_summary": "string"
  }
}
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

Create or fully replace a meal log (enqueues async analysis)

Full-replacement semantics — each `PUT` sends the complete log payload, including on update. Each meal has at most one log. A successful `PUT` enqueues asynchronous analysis; the log's `insight_headline` and `insight_body` populate when the job completes. Status code is `201 Created` on first write, `200 OK` on replacement of an existing log.

JWKS for verifying member bearer tokens

Next Page