Gutlog

Feedback API

Request features, report issues and upvote what matters to you. 14 ops: list_feedback, get_feedback, list_my_feedback, request_feature, report_issue, upvote_feedback, remove_feedback_vote, comment_on_feedback, set_feedback_subscription, submit_review, list_reviews, update_feedback, respond_to_feedba

Request features, report issues and upvote what matters to you.

list_feedback

readno credential needed

List feature requests and issues · POST /api/v1/list_feedback · scope feedback:read or GET …?input=

The Gutlog feedback board: feature requests every customer can see, plus your own issue reports (and ones the team published), with status and upvotes, most upvoted first. Each item says whether your organization voted for it or filed it. Call it before request_feature or report_issue to find an existing item to upvote instead of filing a duplicate, or when the human asks what is planned. Works without a credential (public items only).

curl -X POST https://getgutlog.com/api/v1/list_feedback \  -H "Authorization: Bearer gutlog_…"

get_feedback

readno credential needed

Get a feature request or issue · POST /api/v1/get_feedback · scope feedback:read or GET …?input=

One feedback item with its status, upvotes, comments (oldest first; official answers from the Gutlog team are marked `official`) and its timeline of status changes with the team's notes. Your own issues include the context you attached.

curl -X POST https://getgutlog.com/api/v1/get_feedback \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"id":1}'

list_my_feedback

read

List my feedback and subscriptions · POST /api/v1/list_my_feedback · scope feedback:read or GET …?input=

What your organization filed (every status), the items you get email about (filed, upvoted, commented, followed) with whether you muted them, your organization's review, and whether feedback email reaches you. Use it to follow up on earlier reports.

curl -X POST https://getgutlog.com/api/v1/list_my_feedback \  -H "Authorization: Bearer gutlog_…"

request_feature

write

Request a feature · POST /api/v1/request_feature · scope feedback:write

Files a feature request on the Gutlog board and upvotes it for your organization. Use it when the human wishes Gutlog did something it cannot do yet (an integration, an op, a Meta feature, a dashboard view). It checks for duplicates first: an identical request gets your vote instead, and when likely matches exist nothing is filed and `similar` lists them (filed: false): upvote_feedback the match, or call again with force: true if yours is different. 10 new items per organization a day. The person behind the call gets a thank-you email and one at every status change. Feature requests and comments are public (never who wrote them beyond a first name): no API keys, message content or customer data.

curl -X POST https://getgutlog.com/api/v1/request_feature \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"title":"Let me log a recipe once and reuse it"}'

report_issue

write

Report an issue · POST /api/v1/report_issue · scope feedback:write

Reports a problem with Gutlog itself: a failing or wrong call (pass the request_id from the error or the X-Request-Id header, and the op), a meal that matched the wrong food or got the wrong nutrients, a barcode that was not found, a docs error. Attach context (meal_id, program_id, gtin, the error), never what the person ate or how they feel, so the team can reproduce it; ids are checked against your organization. Issues are private: only your organization and the Gutlog team see them, and the team may publish a sanitized title so others can upvote it. Upvote a matching report from list_feedback (kind issue) instead of filing again; likely duplicates are returned in `similar` with filed: false unless force: true. 10 new items per organization a day. The reporter gets an email with what was captured and one at every status change.

curl -X POST https://getgutlog.com/api/v1/report_issue \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"title":"Let me log a recipe once and reuse it"}'

upvote_feedback

write

Upvote a feature request or issue · POST /api/v1/upvote_feedback · scope feedback:write

Adds your organization's upvote to a feature request or issue ("me too"); votes decide what gets built and fixed first, and you get an email when its status changes. Idempotent: one vote per organization. A vote on a duplicate goes to the original. Returns the item with its new vote count.

curl -X POST https://getgutlog.com/api/v1/upvote_feedback \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"id":1}'

remove_feedback_vote

write

Remove an upvote · POST /api/v1/remove_feedback_vote · scope feedback:write

Takes back your organization's upvote on a feature request or issue, and stops its emails unless you filed or commented on it. Returns the item with its new vote count.

curl -X POST https://getgutlog.com/api/v1/remove_feedback_vote \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"id":1}'

comment_on_feedback

write

Comment on a feature request or issue · POST /api/v1/comment_on_feedback · scope feedback:write

Adds context to an existing feature request or issue: your use case, another failing request, a workaround. Prefer it (with upvote_feedback) over filing a near-duplicate. You then get emails about the item; its author gets a daily digest of new comments. 50 comments per organization a day. Feature requests and comments are public (never who wrote them beyond a first name): no API keys, message content or customer data.

curl -X POST https://getgutlog.com/api/v1/comment_on_feedback \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"id":1,"body":"I cook the same chili every week and re-enter it each time."}'

set_feedback_subscription

write

Start or stop feedback emails · POST /api/v1/set_feedback_subscription · scope feedback:write

With id: start or stop emails about one feature request or issue. Without id: turn every feedback email (thank-yous, status changes, replies) on or off for the person behind this credential. Lifecycle and product emails are separate.

curl -X POST https://getgutlog.com/api/v1/set_feedback_subscription \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"subscribed":false}'

submit_review

write

Post or edit a review · POST /api/v1/submit_review · scope feedback:write

Posts your organization's public review of Gutlog (1–5 stars, what you like, what you don't, what you use it for), or edits it (once an hour; earlier versions are kept). Ask the human for the rating and words; never invent a review or post one they did not approve. It publishes on /reviews right away unless an automated check holds it for a quick look (new accounts, links, profanity). marketing_consent: true lets Meter quote it. The reviewer gets a thank-you email and one when the team replies.

curl -X POST https://getgutlog.com/api/v1/submit_review \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"rating":1}'

list_reviews

readno credential needed

List reviews · POST /api/v1/list_reviews · scope feedback:read or GET …?input=

Published reviews of Gutlog with the aggregate (average rating, count and distribution) and the team's responses. Works without a credential.

curl -X POST https://getgutlog.com/api/v1/list_reviews \  -H "Authorization: Bearer gutlog_…"

update_feedback

write

Update feedback (staff) · POST /api/v1/update_feedback · scope feedback:write

Gutlog team only. Moves an item through open → planned → in_progress → done, or declined, or duplicate (with duplicate_of: votes and subscribers move to the original), with a note every subscriber gets by email. Also publishes or hides an issue (visibility, with a sanitized public_title) and links the GitHub issue or PR (external_ref).

curl -X POST https://getgutlog.com/api/v1/update_feedback \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"id":1}'

respond_to_feedback

write

Respond officially (staff) · POST /api/v1/respond_to_feedback · scope feedback:write

Gutlog team only. Posts an official response on an item (emailed to every subscriber), optionally changing its status in the same call.

curl -X POST https://getgutlog.com/api/v1/respond_to_feedback \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"id":1,"body":"I cook the same chili every week and re-enter it each time."}'

respond_to_review

write

Respond to or moderate a review (staff) · POST /api/v1/respond_to_review · scope feedback:write

Gutlog team only. Replies publicly under a review (the reviewer gets an email), and/or hides or publishes it with a reason. Never hide a review for being negative.

curl -X POST https://getgutlog.com/api/v1/respond_to_review \  -H "Authorization: Bearer gutlog_…" \  -H "Content-Type: application/json" \  -d '{"id":1}'