Report a Candor bug, friction, or idea to the Candor team.

Send one product report about Candor's software. Candor's feedback endpoint stores it and delivers it to the Candor team; it leaves the workspace and does not change any record, note, or approved state. After Candor misbehaves or needs a workaround, the agent offers the report to the user once their task is finished and sends it only when the user agrees or asks for it; it never blocks the user's work. Strip financial and personal data first and describe Candor's behavior with operation names and error codes.

post/v1/feedback

Request

  • Base URL: https://api.candor.money
  • URL: https://api.candor.money/v1/feedback
  • Auth: HTTP bearer

Headers

Idempotency-Keystring required

Stable opaque identity for one logical POST. Reuse only with the same method, path, actor, and body for transport retries. A completed receipt replays its original result, including a refusal; changed input with the same key is rejected. After a refused action and access recovery, use a new key for the new attempt. Follow retryable and recovery guidance if the operation is still running or its outcome is unknown.

Request body

kind'bug' | 'friction' | 'idea' required

bug when an operation did not work as documented or the agent had to work around Candor. friction when something works but took more steps, retries, or guesswork than it should. idea for a capability or change that would have made the user's task easier.

titlestring required

One trimmed summary line without line breaks and with at least one non-space character, such as "notes.update rejects a null revisit_at after resolve". It becomes the report's subject.

bodystring required

Markdown detail with at least one non-space character. State what was attempted, what was expected, and what happened instead, with operation names, error codes, and the workaround used. No financial data.

about_operationstring

The Candor operation id the report concerns, such as notes.update, as listed by candor commands. Omitting it costs triage the exact surface.

about_action_idstring

The action id of the request where the problem occurred, from that response's envelope action.id. It lets triage read the exact operating context; omit it when the report is not about one request.

Response

Stored feedback receipt envelope.

schema_versionstring required
generated_atstring date-time required
request_idstring required
status'success' | 'partial_success' | 'action_required' | 'error' required
user_messagestring

Optional concise user-safe message the calling agent may adapt.

warningsobject[] required
dataobject nullable required

Operation-specific result data, or null when the request ends in an error.

Changes

No recorded changes to this operation across all 1 revision of this API.