Delete item

DELETE /v1/items/:entityTypeId/:id

Deletes a smart process item by ID. A deleted item cannot be restored through the API — create a new one if needed.

Use the entityTypeId field from GET /v1/smart-processes in the /v1/items/:entityTypeId path. The type record's internal id is a different identifier. For example, if a type is returned as { "id": 3, "entityTypeId": 174 }, the path starts with /v1/items/174. Use the returned value rather than assuming all type IDs start at 1030.

Parameters

Examples

The examples use entityTypeId = 177 and id = 783; replace them with your values.

curl — personal key

curl -X DELETE "https://vibecode.bitrix24.com/v1/items/177/783" \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

curl -X DELETE "https://vibecode.bitrix24.com/v1/items/177/783" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"

JavaScript — personal key

const res = await fetch('https://vibecode.bitrix24.com/v1/items/177/783', {
  method: 'DELETE',
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})

if (res.status === 204) {
  console.log('Item deleted')
}

JavaScript — OAuth application

const res = await fetch('https://vibecode.bitrix24.com/v1/items/177/783', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

if (res.status === 204) {
  console.log('Deleted')
}

Response

On success, the API returns 204 No Content with an empty body — check the status code to confirm success.

Response example

HTTP/1.1 204 No Content

Error response example

400 — reserved entityTypeId (for standard CRM entities):

{
  "success": false,
  "error": {
    "code": "INVALID_DYNAMIC_PARAM",
    "message": "entityTypeId 2 has a dedicated API: use /v1/deals instead"
  }
}

Errors

Full list of common API errors — Errors.

See also

• List items
• Create item
• Smart processes
• Limits and optimization