For AI agents: markdown of this page — /docs-content-en/entities/requisite-presets/preset-fields.md documentation index — /llms.txt
Requisite preset fields
Manage the field set of a CRM requisite preset: which fields the preset contains, their captions, their order and whether they appear in the short list. The preset is specified by :presetId in the request path.
Bitrix24 API: crm.requisite.preset.field.*
Scope: crm
Operations
- List preset fields —
GET /v1/requisite-presets/:presetId/fields - Get a preset field —
GET /v1/requisite-presets/:presetId/fields/:id - Add a field to a preset —
POST /v1/requisite-presets/:presetId/fields - Update a preset field —
PATCH /v1/requisite-presets/:presetId/fields/:id - Delete a preset field —
DELETE /v1/requisite-presets/:presetId/fields/:id - Fields available to add —
GET /v1/requisite-presets/:presetId/fields/available - Preset field schema —
GET /v1/requisite-presets/:presetId/fields/schema
Typical scenario
- Pick a preset:
GET /v1/requisite-presets— itsidgoes into the path as:presetId. - Check which fields can be added:
GET /v1/requisite-presets/:presetId/fields/available. - Add a field:
POST /v1/requisite-presets/:presetId/fieldswith afieldNamefrom step 2. - Check the preset's field set:
GET /v1/requisite-presets/:presetId/fields.