Skip to main content
Send POST /feedback with a rating, a message, or field verdicts. Include the task or workflow row when you have it; leave out target to report a problem with the API, docs, or a tool.

Send a report

This example reports a problem with a People Intelligence response. Replace the message with what happened. Reuse the same Idempotency-Key when retrying this report; use a new key for a different report.
The receipt includes the ID to keep for checking status:

Identify the result and correction

Add target and fields to the request when you can identify the result:
Replace the example task ID with the task_id from your async response or webhook. For a synchronous enrichment, use its X-Correlation-ID response header. If a request failed before creating a task, leave out target and include its correlation_id in message. For a workflow row, use {"type":"workflow_row","run_id":"YOUR_JOB_ID","block":2,"row":37}: run_id is the job_id from POST /workflows/run, block is the results file’s block_number, and row is its _row_id. Use wrong for an incorrect value, outdated for a value that was right once, missed when a value exists but we returned nothing, or correct to confirm a value. Leave unreviewed fields out. Leave out correct when you don’t know the right value; an explicit null reports that the right value is empty.

Check review status

Use the receipt’s id with the same team credentials:
The response includes your report, its channel, status, and status_updated_at. Status starts at received, changes to reviewed when the team has examined it, and to fixed when the reported issue is resolved. A status change does not rewrite a result you already downloaded. Access to feedback follows access to its target.

From an MCP agent

Call sixtyfour_send_feedback with the same report in feedback and a stable idempotency_key. Then call sixtyfour_get_feedback with the returned ID to check its status. Ask your agent: “Report this incorrect email to Sixtyfour, include the task ID and evidence, and save the feedback ID.” See the MCP setup guide to connect these tools.

Errors

For error responses (400, 403, etc.), see Handling Errors.