Update requisite

PATCH /v1/requisites/:id

Updates fields of an existing requisite. Pass fields at the root of the request body, without a fields wrapper.

Parameters

Request fields (body)

Pass only the fields you want to change (at least one). All fields are optional. Below are the common fields and a selection of rq* fields. The fields a preset uses are listed by GET /v1/requisite-presets/:presetId/fields. Full list, including fields of all countries and UF_CRM_* user fields — GET /v1/requisites/fields.

Examples

curl — personal key

curl -X PATCH "https://vibecode.bitrix24.com/v1/requisites/42" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "rqInn": "1234567890",
    "rqKpp": "123456789",
    "rqDirector": "John Smith"
  }'

curl — OAuth application

curl -X PATCH "https://vibecode.bitrix24.com/v1/requisites/42" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "rqInn": "1234567890",
    "rqKpp": "123456789"
  }'

JavaScript — personal key

const res = await fetch('https://vibecode.bitrix24.com/v1/requisites/42', {
  method: 'PATCH',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    rqInn: '1234567890',
    rqKpp: '123456789',
    rqDirector: 'John Smith',
  }),
})

const { success, data } = await res.json()

JavaScript — OAuth application

const res = await fetch('https://vibecode.bitrix24.com/v1/requisites/42', {
  method: 'PATCH',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    rqInn: '1234567890',
    rqKpp: '123456789',
  }),
})

const { success, data } = await res.json()

Response fields

Response example

The main fields are shown. Full list: Requisite fields.

{
  "success": true,
  "data": {
    "id": 527,
    "entityTypeId": 4,
    "entityId": 3157,
    "presetId": 1,
    "name": "Primary requisite",
    "active": true,
    "sort": 500,
    "rqInn": "1234567890",
    "rqKpp": "123456789",
    "rqDirector": "John Smith",
    "createdAt": "2026-10-22T08:51:53.000Z",
    "updatedAt": "2026-10-22T08:53:26.000Z",
    "modifyBy": 1
  }
}

Error response example

404 — requisite not found:

{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "The Requisite with ID '999999999' is not found"
  }
}

Errors

Full list of common API errors — Errors.

Known specifics

The preset and owner cannot be changed. presetId, entityTypeId and entityId in the update body are silently ignored: the response is 200 and the values stay the same. To change the preset or move the requisite to another contact or company, create a new requisite and delete the old one.

A field with an unknown name is ignored. A name that is not in GET /v1/requisites/fields is dropped without an error. A field from the schema is saved even if it is not in the requisite preset, for example rqInn on a requisite with the Company preset.

An empty value clears the field. To clear a string requisite field — name, code, xmlId, originatorId or an rq* field — pass an empty string "" or null. For numeric fields (sort) and boolean fields (active, addressOnly, rqVatPayer, rqStampPresent), an empty string is rejected with 400 INVALID_PARAMS as a type mismatch: send null or omit the field. For date fields (rqCompanyRegDate, rqVatCertDate, rqBaseDocDate, rqRegCertDate, rqIdentDocDate), an empty string clears the field. Cleared fields are returned as null in responses.

See also

• Get requisite
• Requisite fields
• Create requisite
• Delete requisite
• Batch
• Limits and optimization