## Remove a reaction

`DELETE /v1/chats/messages/:messageId/reactions/:reaction`

Removes the current user's reaction from a message. The chat is resolved from the message, so no `dialogId` is needed.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|---------|
| `messageId` (path) | number | yes | Message ID, a positive integer — the `messageId` field from the [reactions list](/docs/chats/messages/reactions-list) |
| `reaction` (path) | string | yes | Reaction code in camelCase — the `reaction` field from the [reactions list](/docs/chats/messages/reactions-list). All codes are on the [Add a reaction](/docs/chats/messages/reactions-create) page |

No body and no query parameters are accepted: any body field or query parameter is rejected with `400 INVALID_PARAMS`.

## Examples

### curl — personal key

```bash
curl -X DELETE "https://vibecode.bitrix24.com/v1/chats/messages/1001/reactions/like" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl -X DELETE "https://vibecode.bitrix24.com/v1/chats/messages/1001/reactions/like" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/chats/messages/1001/reactions/like', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

const { data } = await res.json()
console.log('Reaction removed:', data.result)
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/chats/messages/1001/reactions/like', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

const { data } = await res.json()
console.log('Reaction removed:', data.result)
```

## Response fields

| Field | Type | Description |
|------|-----|---------|
| `success` | boolean | Always `true` on success |
| `data.result` | boolean | `true` — the reaction is removed |

## Response example

```json
{
  "success": true,
  "data": {
    "result": true
  }
}
```

## Error response example

422 — the current user has not added this reaction to the message:

```json
{
  "success": false,
  "error": {
    "code": "BITRIX_ERROR",
    "message": "REACTION_NOT_FOUND",
    "b24Code": "REACTION_NOT_FOUND"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 400 | `INVALID_PARAMS` | `messageId` is not a positive integer, the reaction code is not in camelCase (`LIKE`, `face_with`), or a body field or query parameter was passed. Checked before any call to Bitrix24 |
| 404 | `ENTITY_NOT_FOUND` | Bitrix24 reported "not found"; the portal code is in `error.b24Code` |
| 422 | `BITRIX_ERROR` | Bitrix24 returned an error; the code is in `error.b24Code`: `REACTION_NOT_FOUND` — the current user has not added this reaction or the code is unknown to Bitrix24, `MESSAGE_NOT_FOUND` — there is no such message |
| 403 | `SCOPE_DENIED` | The API key does not have the `im` scope |
| 403 | `WRITE_BLOCKED_READONLY_KEY` | A read-only key cannot remove reactions — see [access rights](/docs/access-rights) |
| 401 | `TOKEN_MISSING` | The API key has no Bitrix24 tokens configured |

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

## See also

- [List reactions to a message](/docs/chats/messages/reactions-list)
- [Add a reaction](/docs/chats/messages/reactions-create)
- [Messages](/docs/chats/messages)