Thrive AI Health
Api reference

Delete a meal log

Removes the log; the parent `Meal` is not deleted. Returns `204 No Content`.

DELETE
/v1/users/{user_id}/meals/{meal_id}/log

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

curl -X DELETE "https://loading/v1/users/497f6eca-6276-4993-bfeb-53cbbbba6f08/meals/497f6eca-6276-4993-bfeb-53cbbbba6f08/log"
Empty
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

Read one meal (with embedded log when present)

Returns the full meal record (ingredients, instructions, calories) plus an embedded `log` when the member has logged. `nutrition_plan_id` is `null` when the meal is not plan-associated.

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.