Feedback

Send a problem report or a suggestion to the Resia team with one request. Your servers, your AI agent, and the members of your organization can all send one. Any API key can send a report, a key with the reader scope included.

Send a report

curl --fail-with-body --silent --show-error \
  "$RESIA_API_BASE/v1/feedback" \
  --header "Authorization: Bearer $RESIA_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "kind": "issue",
    "message": "A call that I placed one minute ago returns 404.",
    "related_ids": ["01K9CALL7M8QW2V5C9H4YTB0KD"]
  }'

Field	What it holds
`kind`	`issue` for a problem, `suggestion` for a change that you want. Leave it out when the report is neither.
`message`	The report, from 1 to 10,000 characters.
`related_ids`	Up to 10 IDs of Resia records that the report is about, such as a `call_id`. Resia stores them as sent and does not look them up.

Resia answers 201 with a receipt:

{
  "feedback_id": "01K9FEED7M8QW2V5C9H4YTB0KD",
  "kind": "issue",
  "created_at": "2026-10-13T15:04:05Z"
}

Resia stores the report for the team to read. The API has no route that reads or lists reports, and the team does not answer through the API. For an urgent problem, write to support@resia.ai.

If something fails

401: the request has no valid credential. See Authentication.
422: a field is not valid, for example an unknown kind, an empty message, or more than 10 related_ids. Nothing is stored.

API reference: Report a problem or suggest a change

Tags

Build with AI assistants