Feedback - Croma API

Send feedback when a call returns an error or an empty result you did not expect, an answer is unclear, or the source or field you need does not exist. It works the same from the API and from the submit_feedback MCP tool.

Feedback is reviewed by Croma, never answered, and cannot be listed or read back. It does not spend credits. Leave out credentials, personal data and payment details.

Submit feedback

POST /feedback

Field	Type	Notes
`type`	string	Required. `issue` (something is wrong), `question` (something is unclear) or `request` (something should exist or change).
`content`	string	Required. What happened or what you need, up to 20,000 characters.
`request_id`	string	The `X-Request-Id` of the call it is about, when you have it.

curl https://api.croma.run/feedback \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "type": "request", "content": "Property liens for Bogota are not covered by any endpoint." }'

{
  "data": {
    "id": "fbk_6f1c2b1e-0d6a-4f7e-9a53-2f8f6f0d9a11",
    "created_at": "2026-10-23T18:04:11.000Z",
    "status": "received"
  }
}

Resending the same report the same day is safe: you get the original id back with "status": "already_received", so if a call times out, send it again. The limit is 20 reports per hour per organization. Past it, the response is a 429 with a Retry-After header.

Full reference

Request and response schemas for every endpoint.