---
title: "Enable or disable patient-data (PHI) sync to the connected CRM."
method: PATCH
path: "/api/v1/crm/connection/phi-sync"
tags: ["CRM · Connection"]
---

# Enable or disable patient-data (PHI) sync to the connected CRM.

`PATCH /api/v1/crm/connection/phi-sync`

## Request

- Base URL: `https://api-dev.fusehealth.com`
- URL: `https://api-dev.fusehealth.com/api/v1/crm/connection/phi-sync`
- Auth: API key in header `x-api-key`

Toggles PHI egress to the clinic's connected CRM. Enabling requires `baaAttested: true` in the body AND the verified BAA on file with FUSE — otherwise 403 `CRM_BAA_REQUIRED`. Disabling is always permitted. 409 if no CRM is connected. Requires the `write` scope.

## Request body

- object
  - `phiSyncEnabled` boolean, required
  - `baaAttested` boolean: Must be true when enabling — confirms the brand holds a BAA with its CRM provider.

## Response `200`

Updated

- object
  - `success` boolean
  - `data` object

## Other responses

- `400`: Bad request / business-rule failure (may include a `code`)
- `401`: Missing, invalid, inactive, or expired API key (or JWT)
- `403`: Authenticated but not permitted (insufficient scope, wrong role, or FUSE feature not enabled)
- `409`: No CRM connected for this clinic.

---

[API](https://skmtc.dev/fusehealth/apis/fuse-brand-api-external.md) · [All operations](https://skmtc.dev/fusehealth/apis/fuse-brand-api-external/llms.txt) · [OpenAPI document](https://skmtc.dev/fusehealth/apis/fuse-brand-api-external/revisions/50821832728c?raw)