---
title: "Submit feedback"
method: POST
path: "/feedback"
tags: ["Feedback"]
---

# Submit feedback

`POST /feedback`

Submits product feedback about Sequenzy itself to the Sequenzy team - for example, when a workflow you or your user needed is not exposed via the API, CLI, or MCP server.

## Request body

- object
  - `message` string, required — The feedback itself. Be specific about what was needed and what was missing or wrong.
  - `category` 'missing_capability' | 'bug' | 'docs' | 'ux' | 'praise' | 'other' — Feedback category. Use missing_capability when a needed workflow is not supported. Defaults to other.
  - `source` 'api' | 'cli' | 'mcp' — Where the feedback was submitted from. Defaults to api.
  - `context` string — Optional description of what you were trying to accomplish when you hit the gap.
  - `userIntent` string — For bug or wrong-outcome reports - the user's request, verbatim or closely paraphrased. Omit personal data not needed to reproduce the problem.
  - `toolCalls` object[] — For bug or wrong-outcome reports - the ordered API calls, CLI commands, or MCP tool calls that led to the problem. Summarize arguments; do not include raw subscriber data.
    - `tool` string, required — Tool, command, or endpoint name.
    - `args` string — Short summary of the arguments used.
    - `error` string — Error returned by this call, if any.
  - `expected` string — What you expected to happen.
  - `actual` string — What actually happened instead.
  - `resourceIds` string[] — IDs of the affected resources so the team can correlate the report with server logs.

## Response `200`

Feedback received

- object
  - `success` boolean
  - `message` string

## Other responses

- `400` — Validation error
- `401` — Unauthorized
- `403` — No company selected
- `500` — Feedback could not be delivered

## Changes

- **2026-08-19** `ba3a29c6eb33` — 4 info
  - added the optional property `retryable` to the response with the `400` status
  - added the optional property `retryable` to the response with the `401` status
  - added the optional property `retryable` to the response with the `403` status
  - added the optional property `retryable` to the response with the `500` status
- **2026-08-16** `6fd2903b91ce` — 4 info
  - added the optional property `code` to the response with the `400` status
  - added the optional property `code` to the response with the `401` status
  - added the optional property `code` to the response with the `403` status
  - added the optional property `code` to the response with the `500` status
- **2026-08-10** `16ad4f8e3d97` — 5 info
  - added the new optional request property `actual`
  - added the new optional request property `expected`
  - added the new optional request property `resourceIds`
  - added the new optional request property `toolCalls`
  - …1 more
- **2026-08-02** `36f92fc0caa2` — 4 breaking
  - the response property `success` became optional for the status `400`
  - the response property `success` became optional for the status `401`
  - the response property `success` became optional for the status `403`
  - the response property `success` became optional for the status `500`
- **2026-07-10** `1b0d5fa83cd8` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/sequenzy/apis/sequenzy-api/changes/feedback/post.md)

---

[API](https://skmtc.dev/sequenzy/apis/sequenzy-api.md) · [All operations](https://skmtc.dev/sequenzy/apis/sequenzy-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/sequenzy/sequenzy-api/revisions/721dbe59409a/schema)