For AI agents: markdown of this page — /docs-content-en/entities/leads/products-delete.md documentation index — /llms.txt

Delete a product from a lead

DELETE /v1/leads/:id/products/:rowId

Deletes a single product row from a lead by row ID. A deleted row cannot be restored via the API — add a new one if needed.

Parameters

Parameter Type Required Description
id (path) number yes Lead ID. List: GET /v1/leads
rowId (path) number yes Product row ID. List: GET /v1/leads/:id/products, or the response of POST /v1/leads/:id/products when adding

rowId is the product row ID, not the catalog productId.

Examples

curl — personal key

Terminal 
curl -X DELETE "https://vibecode.bitrix24.com/v1/leads/312/products/1465" \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

Terminal 
curl -X DELETE "https://vibecode.bitrix24.com/v1/leads/312/products/1465" \
  -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/leads/312/products/1465', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

if (res.status === 204) {
  console.log('Product removed from the lead')
}

JavaScript — OAuth application

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/leads/312/products/1465', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

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

Response

On successful deletion, HTTP status 204 No Content is returned with an empty body — check the status to confirm success.

Response example

HTTP/1.1 204 No Content

Error response example

404 — product row not found:

JSON 
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "Item not found"
  }
}

Errors

HTTP Code Description
404 ENTITY_NOT_FOUND No product row with this rowId
400 INVALID_ROW_ID rowId is not a positive integer
403 SCOPE_DENIED API key lacks the crm scope
403 WRITE_BLOCKED_READONLY_KEY The key is read-only — see access rights
401 TOKEN_MISSING API key has no configured tokens

Full list of common API errors — Errors.

See also