> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/api/guides/feedback.md).

# Feedback

Report FLORA API bugs, feature requests and missing capabilities from your code with the feedback endpoint.

Use the feedback endpoint to tell FLORA when an API workflow is blocked or needs something new. It's most useful when an endpoint rejects something you expected to work, such as a source URL FLORA couldn't fetch.

## Record feedback

```bash
curl -X POST https://app.flora.ai/api/v1/feedback \
  -H "Authorization: Bearer $FLORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "missing_capability",
    "summary": "Asset upload from Instagram CDN URLs fails",
    "detail": "POST /assets with source https://scontent-lga3-1.cdninstagram.com/... was rejected.",
    "attempted_tools": ["POST /assets"],
    "workspace_id": "ws_abc123"
  }'
```

Response (`201 Created`):

```json
{
  "feedback_id": "fb_abc123",
  "received_at": "2026-05-22T14:30:00.000Z"
}
```

With the TypeScript SDK:

```ts
await client.feedback.record({
  kind: "bug",
  summary: "Run stuck in running for an hour",
  detail: "run_abc123 started at 14:02 UTC and still reports running.",
  run_id: "run_abc123",
})
```

## Request fields

See [Record feedback](https://docs.flora.ai/api/reference/feedback/recordfeedback.md) in the reference for the full schema.

| Field             | Required | Notes                                                                                       |
| ----------------- | -------- | ------------------------------------------------------------------------------------------- |
| `kind`            | Yes      | One of `feature_request`, `bug`, `technique_request`, `missing_capability`                  |
| `summary`         | Yes      | A short summary of the request or issue                                                     |
| `detail`          | Yes      | What you tried: the endpoint, the rejected value, or the workflow                           |
| `attempted_tools` | No       | Endpoints or FLORA MCP tool names you tried, such as `POST /assets` or `flora_create_asset` |
| `workspace_id`    | No       | Public workspace ID, starting with `ws_`                                                    |
| `project_id`      | No       | Public project ID, starting with `prj_`                                                     |
| `run_id`          | No       | Public run ID, starting with `run_`                                                         |

## Common validation issues

* `kind`, `summary` and `detail` are required.
* Use `kind: "missing_capability"` when the API correctly rejects something it doesn't support yet.
* Optional IDs must use public prefixes (`ws_`, `prj_`, `run_`).

Feedback isn't a support ticket. If something is broken for you right now, email <support@florafauna.ai> with the `Flora-Request-Id`; see [Errors](https://docs.flora.ai/api/platform/errors.md#contacting-support).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flora.ai/api/guides/feedback.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
