# PATCH /feedback/:feedback_id

**Resource:** [FEEDBACK](./feedback.md)  
**MCP tool:** `update_feedback`  
**Scopes:** `feedback:write`  
**Write operation:** yes

Update customer feedback: move its status, assign it, add what was done, or correct what was recorded.

## Parameters

| Name | In | Type | Required | Description |
|------|----|------|----------|-------------|
| `feedback_id` | path | string | yes | The feedback id. |
| `status` | body | string | no | logged, needs_attention, in_progress or resolved. Moving to resolved stamps who resolved it and when. |
| `assigned_to` | body | string | no | User id of the team member following it up. Send null to unassign. |
| `resolution_note` | body | string | no | What was done about it. |
| `summary` | body | string | no | One line on what the customer said. |
| `details` | body | string | no | What they said in full. |
| `rating` | body | number | no | Their rating from 1 to 5. |
| `sentiment` | body | string | no | positive, mixed or negative. |
| `require_approval` | body | boolean | no | Optional. Set true to route this write into the approval queue for human review instead of executing it immediately (returns 202 + an approval_id). Works even when your key/token has permission to execute directly. |

## Request example

```bash
curl -X PATCH   "https://api.trustpager.com/functions/v1/api/v1/feedback/:feedback_id"   -H "Authorization: Bearer YOUR_API_KEY"   -H "Content-Type: application/json"   -d '{"status":"...","assigned_to":"...","resolution_note":"..."}'
```

---
Base URL: `https://api.trustpager.com/functions/v1/api/v1` — Auth: `Authorization: Bearer YOUR_API_KEY`