For AI agents: markdown of this page — /docs-content-en/openlines/sessions/start.md documentation index — /llms.txt
Start a session
POST /v1/openlines/sessions/start
Picks up an Open Channel dialog: the employee the call runs as becomes the operator of the chat session.
The action runs on behalf of the employee the key belongs to — see On whose behalf the action runs.
Request fields (body)
| Field | Type | Required | Description |
|---|---|---|---|
FieldchatId |
Typenumber | string | Requiredyes | DescriptionOpen Channel chat identifier, a positive integer. A string is accepted if it consists of digits only and does not start with zero. See Chat ID |
Examples
curl — personal key
curl -X POST https://vibecode.bitrix24.com/v1/openlines/sessions/start \
-H "X-Api-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"chatId": 5255}'
curl — OAuth application
curl -X POST https://vibecode.bitrix24.com/v1/openlines/sessions/start \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{"chatId": 5255}'
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/openlines/sessions/start', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_API_KEY',
'Content-Type': 'application/json',
},
body: JSON.stringify({ chatId: 5255 }),
})
const { success, data, error } = await res.json()
if (!success) throw new Error(`${error.code}: ${error.message}`)
console.log('Session started:', data.started)
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/openlines/sessions/start', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
'Content-Type': 'application/json',
},
body: JSON.stringify({ chatId: 5255 }),
})
const { success, data } = await res.json()
Response fields
| Field | Type | Description |
|---|---|---|
Fieldsuccess |
Typeboolean | Descriptiontrue on a successful call |
Fielddata.chatId |
Typenumber | DescriptionChat identifier from the request. A string from the request is returned as a number |
Fielddata.started |
Typeboolean | DescriptionAlways true |
Response example
{
"success": true,
"data": {
"chatId": 5255,
"started": true
}
}
Error response example
404 — no chat with this chatId:
{
"success": false,
"error": {
"code": "ENTITY_NOT_FOUND",
"message": "Open Line chat not found"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| HTTP400 | CodeINVALID_CHAT_ID |
DescriptionchatId is missing, is not a positive integer, is a string with non-digit characters or a leading zero, or is greater than 9007199254740991 |
| HTTP404 | CodeENTITY_NOT_FOUND |
DescriptionNo chat with this chatId |
| HTTP422 | CodeBITRIX_ERROR |
DescriptionBitrix24 refused the action. Its code is in error.b24Code |
| HTTP403 | CodeBITRIX_ACCESS_DENIED |
DescriptionThe employee the call runs as has no permission for the action |
| HTTP502 | CodeOPENLINE_OPERATOR_FAILED |
DescriptionBitrix24 neither confirmed the action nor returned an error |
| HTTP403 | CodeSCOPE_DENIED |
DescriptionThe key has no imopenlines scope |
| HTTP403 | CodeWRITE_BLOCKED_READONLY_KEY |
DescriptionThe key is read-only |
| HTTP401 | CodeMISSING_API_KEY |
DescriptionThe X-Api-Key header is missing |
| HTTP401 | CodeINVALID_API_KEY |
DescriptionThe key is not recognized |
| HTTP401 | CodeTOKEN_MISSING |
DescriptionA personal key has no access to the Bitrix24 portal, or an application key was sent without a session token in Authorization |
| HTTP502 | CodeBITRIX_UNAVAILABLE |
DescriptionBitrix24 is unavailable or the connection to it broke before the response was complete |
Full list of common API errors — Errors.
Known specifics
- A closed chat is opened with a new session. If the chat has no open session, the call creates a new one with the status
answered, and its operator is the employee the call runs as. The new session appears in the session search with the samechatId. - A repeated call does not create a second session. If the employee is already the operator of the chat's open session, the response is again
started: true, and the session stays the same.