# Sync a single co-sell referral with the partner / CRM

`POST https://api.suger.cloud/org/{orgId}/cosell/referral/{referralId}/sync`

Trigger a one-way sync for a specific referral. Controlled by `direction`:
- OUTBOUND: CRM -> Suger -> Partner (push local changes to the cloud partner)
- INBOUND (default): Partner -> Suger -> CRM (pull partner-side updates into Suger and CRM)

This is the primary way to push a Suger-side edit to the partner after calling UpdateCosellReferral, and to refresh Suger with the partner's latest stage/status for an inbound referral.

Side effect: for AWS / Azure / GCP, calls the partner API (AWS ACE / Azure Partner Center / GCP) and writes back to Suger DB + linked CRM record (Salesforce / HubSpot / Dynamics 365). `partner=SUGER` referrals (Suger PRM peer-to-peer) are not exposed through this MCP tool.

Use this when: user wants to "submit", "push", "refresh", or "sync" one referral.

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `orgId` | path | string | yes | Organization ID |
| `referralId` | path | string | yes | Cosell Referral ID |
| `direction` | query | string | no | Sync direction: INBOUND or OUTBOUND (default INBOUND) |

## Responses

### 200 — OK

Content-Type: `application/json` · Schema: `OperationExecutionDetails`

### 400 — Bad request error

Content-Type: `application/json` · Schema: `ErrorResponse`

### 404 — Referral not found

Content-Type: `application/json` · Schema: `ErrorResponse`

### 500 — Internal server error

Content-Type: `application/json` · Schema: `ErrorResponse`

---

Interactive API reference: https://doc.suger.io/api/