---
title: Feedback | FLORA API
description: Report public API bugs, feature requests, and missing capabilities.
---

Use feedback to tell FLORA when an API workflow is blocked or needs a new capability. This is especially useful when an endpoint returns a validation error for something you expected to work, such as an unsupported asset source host.

## Record feedback

Terminal window

```
curl -X POST https://app.flora.ai/api/v1/feedback \
  -H "Authorization: Bearer sk_live_XXXX" \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "missing_capability",
    "summary": "Need support for Instagram CDN asset URLs",
    "detail": "upload-asset rejected an image hosted on scontent-lga3-1.cdninstagram.com.",
    "attempted_tools": ["upload-asset"],
    "workspace_id": "ws_abc123"
  }'
```

Response (`201 Created`):

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

## Request fields

| Field             | Required | Notes                                                                               |
| ----------------- | -------- | ----------------------------------------------------------------------------------- |
| `kind`            | Yes      | One of `feature_request`, `bug`, `technique_request`, `missing_capability`          |
| `summary`         | Yes      | Short summary of the request or issue                                               |
| `detail`          | Yes      | Detailed description with the endpoint, rejected value, or workflow you attempted   |
| `attempted_tools` | No       | Endpoint or MCP tool names you tried, such as `upload-asset` or `create-generation` |
| `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 a currently unsupported workflow, such as a source URL host that is not allowlisted.
- Optional IDs must use public API prefixes (`ws_`, `prj_`, `run_`).