REST API reference
Every op, its input schema and a curl example, generated from the ops registry.
Every action in Gutlog is an op. Call one with POST https://getgutlog.com/api/v1/{op} and its input as a JSON body. Read-only ops also answer GET with the input as URL-encoded JSON in ?input=. This page is generated from the same registry that serves the API, so it lists exactly what the API accepts.
- Auth:
Authorization: Bearer gutlog_…(orX-Api-Key). A scoped key can call only the ops its scopes cover. With an OAuth or session token, pick an organization withx-gutlog-org: <slug>. - Errors are RFC 9457
application/problem+jsonwith acodeandrequest_id: see Errors. - Machine-readable: OpenAPI 3.1, the op catalog and llms-full.txt.
Your first call
curl -X POST https://getgutlog.com/api/v1/get_account \ -H "Authorization: Bearer gutlog_…"get_pricing and create_checkout_link answer without a credential (also as GET /api/v1/pricing). Groups with no ops yet are still being built; GET /api/v1 always lists exactly what is live.
All ops
Each group has its own page with every op's description, access, input schema and curl and CLI examples.
Meals and diary
log_mealget_dayget_meallist_review_queueupdate_mealconfirm_ingredientsreject_ingredientsadd_ingredientsset_nutrientsmark_revieweddelete_mealcopy_mealsave_personal_foodlist_personal_foodsarchive_personal_foodrate_analysisget_calibrationget_calibration_allrefresh_global_aliasesget_logging_settingsupdate_logging_settings