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
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):
{
"feedback_id": "fb_abc123",
"received_at": "2026-05-22T14:30:00.000Z"
}With the TypeScript SDK:
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 in the reference for the full schema.
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,summaryanddetailare 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 [email protected] with the Flora-Request-Id; see Errors.
Last updated
Was this helpful?