For AI agents: markdown of this page — /docs-content-en/mail/conversions/crm-activity-create.md documentation index — /llms.txt
Create a CRM activity from a message
POST /v1/mail/messages/:id/crm-activity
Creates a CRM activity from a message and links the message to CRM. No request body is required — the message identifier is taken from the path.
Parameters
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
id |
path | integer | yes | Message identifier. List: GET /v1/mail/messages |
Examples
curl — personal key
curl -X POST \
-H "X-Api-Key: YOUR_API_KEY" \
https://vibecode.bitrix24.com/v1/mail/messages/123/crm-activity
curl — OAuth application
curl -X POST \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN" \
https://vibecode.bitrix24.com/v1/mail/messages/123/crm-activity
JavaScript — personal key
const res = await fetch(
'https://vibecode.bitrix24.com/v1/mail/messages/123/crm-activity',
{
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_API_KEY',
},
}
)
const body = await res.json()
if (!body.success) throw new Error(body.error.code)
console.log(`Activity created: ${body.data.result}`)
JavaScript — OAuth application
const res = await fetch(
'https://vibecode.bitrix24.com/v1/mail/messages/123/crm-activity',
{
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
}
)
Response fields
| Field | Type | Description |
|---|---|---|
success |
boolean | true on success |
data.result |
boolean | true when the CRM activity is created |
Response example
{
"success": true,
"data": {
"result": true
}
}
Error response example
400 — the message is from a Bitrix24 portal employee:
{
"success": false,
"error": {
"code": "INVALID_PARAMS",
"message": "Request object validation failed",
"validation": [
{
"message": "Emails to employees cannot be saved to CRM"
}
]
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 400 | INVALID_PARAMS |
Non-numeric or negative :id in the path — message id must be a positive integer |
| 400 | INVALID_PARAMS |
The message is from a Bitrix24 portal employee or the message is deleted. The reason is in the validation array |
| 401 | MISSING_API_KEY |
The X-Api-Key header is missing |
| 401 | INVALID_API_KEY |
Invalid or expired key |
| 401 | KEY_INACTIVE |
The key is deactivated |
| 401 | KEY_EXPIRED |
The key has expired |
| 401 | TOKEN_MISSING |
The key is not linked to a Bitrix24 portal |
| 403 | SCOPE_DENIED |
The key lacks the mail scope |
| 422 | BITRIX_ERROR |
Other Bitrix24 errors |
| 429 | RATE_LIMITED |
Request limit exceeded |
| 502 | BITRIX_UNAVAILABLE |
Bitrix24 is unavailable |
The full list of common API errors — Errors.
Known specifics
- An activity is created only for messages from external senders.
- A repeated call for a message that already has an activity returns the same successful response and does not create a second activity — the operation is idempotent.