## Replace lead contacts

`PUT /v1/leads/:id/contacts`

Replaces the whole set of lead contacts in one call: links the contacts from the list and unlinks all others.

To add one contact without unlinking the others, use [`POST /v1/leads/:id/contacts`](/docs/entities/leads/contacts-create).

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|----------|
| `id` (path) | number | yes | Lead ID. List: [`GET /v1/leads`](/docs/entities/leads/list) |

## Request fields (body)

| Field | Type | Required | Description |
|------|-----|:-----:|----------|
| `items` | array | yes | The new set of lead contacts, including already linked contacts that must stay. Contacts missing from the array are unlinked. An empty array `[]` unlinks all contacts |
| `items[].contactId` | number | yes | Contact ID. List: [`GET /v1/contacts`](/docs/entities/contacts/list) |
| `items[].isPrimary` | boolean | no | Primary contact of the lead. If no element has `true`, the first array element becomes primary. If several elements have `true`, the first of them does |
| `items[].sort` | number | no | Position of the contact in the list. If omitted, it is set by the element's position: `10` for the first, `20` for the second |

## Examples

### curl — personal key

```bash
curl -X PUT "https://vibecode.bitrix24.com/v1/leads/1001321/contacts" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "items": [
      { "contactId": 2941, "sort": 10 },
      { "contactId": 2937, "isPrimary": true, "sort": 20 }
    ]
  }'
```

### curl — OAuth application

```bash
curl -X PUT "https://vibecode.bitrix24.com/v1/leads/1001321/contacts" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "items": [
      { "contactId": 2941, "sort": 10 },
      { "contactId": 2937, "isPrimary": true, "sort": 20 }
    ]
  }'
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/leads/1001321/contacts', {
  method: 'PUT',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    items: [
      { contactId: 2941, sort: 10 },
      { contactId: 2937, isPrimary: true, sort: 20 },
    ],
  }),
})

const { success, data } = await res.json()
console.log('Lead contacts:', data.length)
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/leads/1001321/contacts', {
  method: 'PUT',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    items: [
      { contactId: 2941, sort: 10 },
      { contactId: 2937, isPrimary: true, sort: 20 },
    ],
  }),
})

const { success, data } = await res.json()
```

## Response fields

| Field | Type | Description |
|------|-----|----------|
| `success` | boolean | Always `true` on success |
| `data` | array | All links of the lead after the replacement, in `sort` order. An empty array after `"items": []` |
| `data[].contactId` | number | Contact ID. Get the contact: [`GET /v1/contacts/:id`](/docs/entities/contacts/get) |
| `data[].isPrimary` | boolean | Primary contact of the lead. `true` on exactly one link |
| `data[].sort` | number | Position of the contact in the list |
| `data[].roleId` | number | Role of the contact in the lead. The link methods do not store it |

## Response example

```json
{
  "success": true,
  "data": [
    { "contactId": 2941, "sort": 10, "isPrimary": false, "roleId": 0 },
    { "contactId": 2937, "sort": 20, "isPrimary": true, "roleId": 0 }
  ]
}
```

## Error response example

400 — the body has no `items` array:

```json
{
  "success": false,
  "error": {
    "code": "INVALID_PARAMS",
    "message": "items must be an array (use [] to unlink all)"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|----------|
| 400 | `INVALID_PARAMS` | `id` is not a positive integer |
| 400 | `INVALID_PARAMS` | `items` is missing or is not an array |
| 400 | `INVALID_PARAMS` | An `items` element is not an object. The message starts with the element index: `items[0] must be an object` |
| 400 | `INVALID_PARAMS` | An `items` element has no `contactId`, or `contactId` is not a positive integer. The message names the element index: `items[0] requires 'contactId'` |
| 404 | `ENTITY_NOT_FOUND` | No lead with this `id` exists |
| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |
| 401 | `TOKEN_MISSING` | The key has no Bitrix24 tokens attached |
| 403 | `SCOPE_DENIED` | The key does not have the `crm` scope |
| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode. Replacement requires a key with write access |
| 429 | `RATE_LIMITED` | Rate limit exceeded. Retry after the delay in the `Retry-After` header |
| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable. Retry the request later |

Full list of common API errors — [Errors](/docs/errors).

## Known specifics

- **Contact existence is not checked.** An ID that matches no contact is linked without an error and appears in the lead's list of links. Before the replacement, check the contacts with [`GET /v1/contacts/:id`](/docs/entities/contacts/get).
- **The role is not stored.** The `roleId` field in an `items` element is accepted without an error but is not stored: in the response, the new link has `roleId` equal to `0`.

## See also

- [Lead contacts](/docs/entities/leads/contacts)
- [List lead contacts](/docs/entities/leads/contacts-list)
- [Link a contact to a lead](/docs/entities/leads/contacts-create)
- [Unlink a contact from a lead](/docs/entities/leads/contacts-delete-delete)
- [Unlink all contacts from a lead](/docs/entities/leads/contacts-delete)
- [Contacts](/docs/entities/contacts)