# partners_update

> Update an existing vendor partner's information or status.

<!-- Source: https://docs.actuallycare.com/tools/partners/partners_update -->

```text
Update an existing vendor partner's information or status. Only provided fields are updated - omitted fields remain unchanged. Common uses: status change (onboarding->active->preferred), tier upgrade, update notes. Returns the updated partner record.
```

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `partner_id` | string | Yes | UUID of the partner to update (required). Use [`partners_list`](/tools/partners/partners_list) to find. · Format: UUID |
| `contact_id` | string | No | Updated contact ID. Use [`contacts_list`](/tools/contacts/contacts_list) to find. · Format: UUID |
| `vendor_type` | string | No | Updated vendor type |
| `title` | string | No | Updated title |
| `status` | enum | No | Updated status · One of: `onboarding`, `active`, `preferred`, `paused`, `churned` |
| `tier` | enum | No | Updated partner tier · One of: `standard`, `preferred`, `vip` |
| `partner_since` | string | No | Updated partnership start date (Format: YYYY-MM-DD) · Format: Date (YYYY-MM-DD) |
| `notes` | string | No | Updated notes |
| `tags` | array of strings | No | Updated tags array (replaces existing tags) |
| `care_status` | enum | No | Care status for tracking. Setting this also updates the audit columns. · One of: `no_status`, `cared`, `needs_care`, `didnt_care` |
| `care_status_note` | string | No | Note explaining the care status change. |
| `record_data` | object (free-form) | No | Pipeline-specific vertical data as a JSON object. Replaces (does not merge with) the existing record_data. |

## Example prompts

- "Bump Dana Whitfield to VIP tier, she closed three escrows with us this quarter."
- "Mark Marcus Webb as needs care and note we haven't touched base since April."

## Safety

**Updates data.** Changes an existing record. The change is visible immediately in the app and can be edited back.