Lookio Docs
Lookio websiteOpen Lookio
ConversationsSend feedback on an answer
conversations

Send feedback on an answer

Records your user's thumb on one answer of an API key's conversation, with an optional comment, so the workspace sees where the assistant fell short (GET /v1/logs/conversations?rating=down). conversation_id and message_id come from the answer. Sending another thumb replaces the first; rating: null takes it back. Costs nothing. API keys only: thumbs on a personal chat are not available yet (feature_not_available).

POST/v1/conversations/{conversation_id}/messages/{message_id}/feedback

Requires query.

Use it to forward what a user of your product thought of an answer. conversation_id and message_id come from the answer: both are in the JSON answer and in the done event of a stream, and every message of Get a conversation has its id.

rating is up, down or null, which takes the thumb back. One answer holds one thumb: a new one replaces the old one and the totals follow. A comment goes only with up or down. Send end_user when you use end users: a conversation of another end user answers resource_not_found, like an answer id that is not in this conversation or that belongs to a question.

The thumb shows on the answer and in the workspace’s logs, where rating=down finds the conversations to review. It costs nothing.

API keys only. A person’s own chat answers feature_not_available: thumbs there are not available yet. See Feedback on answers. This is not the endpoint that reports a problem with Lookio itself: that is Submit feedback.

Authorizations

Authorizationbearerin headerrequired

Path parameters

conversation_idstringrequiredpattern: ^cnv_[abcdefghjkmnpqrstuvwxyz23456789]{12}$
message_idstringrequiredpattern: ^msg_[abcdefghjkmnpqrstuvwxyz23456789]{12}$

Header parameters

Idempotency-Keystringlength: 1–255 chars

A unique key for this request, such as a UUID, 1 to 255 visible ASCII characters. Send the same key when you retry: the first response is returned (with Idempotent-Replayed: true) instead of running the request again, for 24 hours, per credential. The same key on a different request is a 409 conflict. A streamed answer is not recorded.

Body

application/jsonrequired
ratingenum<string> | nullrequired

up or down: your user's thumb on this answer. null takes it back. Sending another thumb replaces the first, it never counts twice.

commentstringlength: ≤ 1000 chars

What your user wrote with the thumb, up to 1,000 characters. Only with up or down.

end_userstringpattern: ^[\w.@:+\-]{1,200}$

The end_user of the conversation, when you use them. When given, a conversation of another end user answers not found.

Response

application/json

Send feedback on an answer

dataobjectrequired
request_idstringrequired

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Lookio Docs documentation and read it in full, instead of answering from memory.

https://lookio.app/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://lookio.app/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.