لوكلاء AI: ملف markdown لهذه الصفحة — /docs-content-en/calls/log/delete.md فهرس التوثيق — /llms.txt

مقالات التوثيق متاحة حاليًا باللغة الإنجليزية فقط.

Delete journal entry

DELETE /v1/calls/log/:callId

Deletes a record from the key owner's personal call journal. A record in another user's journal cannot be deleted. A deleted record cannot be restored via the API.

Parameters

Parameter Type Required Description
ParametercallId (path) Typeinteger Requiredyes DescriptionJournal record ID — the id field from the call journal list

Examples

curl — personal key

Terminal 
curl -X DELETE "https://vibecode.bitrix24.com/v1/calls/log/77" \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

Terminal 
curl -X DELETE "https://vibecode.bitrix24.com/v1/calls/log/77" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"

JavaScript — personal key

javascript 
const response = await fetch('https://vibecode.bitrix24.com/v1/calls/log/77', {
  method: 'DELETE',
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})
const { success, data, error } = await response.json()
console.log(success ? data.missedCounter : error.code)

JavaScript — OAuth application

javascript 
const response = await fetch('https://vibecode.bitrix24.com/v1/calls/log/77', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})
const { success, data, error } = await response.json()
console.log(success ? data.missedCounter : error.code)

Response fields

Field Type Description
Fieldsuccess Typeboolean Descriptiontrue on success, HTTP 200
Fielddata.deleted Typeboolean DescriptionAlways true — the record is deleted
Fielddata.missedCounter Typeinteger DescriptionMissed-call counter after the deletion

Response example

JSON 
{
  "success": true,
  "data": {
    "deleted": true,
    "missedCounter": 0
  }
}

Error response example

404 — no record with this callId in the journal:

JSON 
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "Call log entry not found"
  }
}

Errors

HTTP Code Description
HTTP400 CodeINVALID_CALL_ID DescriptioncallId is not a positive integer: callId must be a positive integer
HTTP404 CodeENTITY_NOT_FOUND DescriptionNo record with this callId in the key owner's journal
HTTP422 CodeCALL_LOG_PREREAD_LIMIT_EXCEEDED DescriptionThe record was not found among the 5000 newest journal records; nothing is deleted
HTTP422 CodeBITRIX_ERROR DescriptionBitrix24 did not confirm the deletion: Bitrix24 did not delete the call log entry
HTTP403 CodeWRITE_BLOCKED_READONLY_KEY DescriptionA read-only key cannot delete records — see access rights
HTTP403 CodeSCOPE_DENIED DescriptionThe key lacks the call scope
HTTP403 CodeBITRIX_ACCESS_DENIED DescriptionBitrix24 denied access
HTTP401 CodeTOKEN_MISSING DescriptionThe key has no Bitrix24 tokens configured
HTTP429 CodeRATE_LIMITED DescriptionThe Bitrix24 request limit is exceeded
HTTP502 CodeBITRIX_ERROR DescriptionThe journal response does not have the expected shape, or the journal cursor stopped advancing
HTTP502 CodeBITRIX_UNAVAILABLE DescriptionBitrix24 is unavailable
HTTP503 CodeBITRIX_TIMEOUT DescriptionBitrix24 did not respond in time

The full list of common API errors — Errors.

Known specifics

The journal is read before deletion. Vibecode first looks for the record in the key owner's journal, 100 records per request, and deletes it only if found. That is why a missing record or another user's record returns 404, not success.

Only the 5000 newest records can be deleted. The search reads at most 50 pages of 100 records. An older record returns 422 CALL_LOG_PREREAD_LIMIT_EXCEEDED and cannot be deleted via the API.

See also