## Get requisite

`GET /v1/requisites/:id`

Returns a requisite by ID with all fields available in its preset (the preset defines the field set: name, INN/KPP/OGRN, director, accountant, etc.).

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|---------|
| `id` (path) | number | yes | Requisite ID |

## Examples

### curl — personal key

```bash
curl "https://vibecode.bitrix24.com/v1/requisites/42" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth app

```bash
curl "https://vibecode.bitrix24.com/v1/requisites/42" \
  -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/requisites/42', {
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

const { success, data } = await res.json()
console.log('Requisite:', data.rqName, '— INN', data.rqInn)
```

### JavaScript — OAuth app

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/requisites/42', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

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

## Response fields

| Field | Type | Description |
|------|-----|---------|
| `success` | boolean | Always `true` on success |
| `data` | object | Requisite object |
| `data.id` | number | Requisite identifier |
| `data.entityTypeId` | number | Parent entity type: `3` — contact, `4` — company |
| `data.entityId` | number | Parent entity ID |
| `data.presetId` | number | ID of the [requisite preset](/docs/entities/requisite-presets) |
| `data.name` | string | Requisite name in the interface |
| `data.active` | boolean | Whether the requisite is active |
| `data.sort` | number | Sort order |
| `data.createdAt` / `data.updatedAt` | datetime | Creation and modification dates (ISO 8601) |
| `data.createdBy` / `data.modifyBy` | number \| null | Creator / last editor ID |
| `data.rqName` / `data.rqInn` / `data.rqKpp` / `data.rqOgrn` | string \| null | Core legal-entity requisites |

Preset fields that are not filled are returned as `null`. Full list of fields — [Requisite fields](/docs/entities/requisites/fields).

## Response example

```json
{
  "success": true,
  "data": {
    "id": 42,
    "entityTypeId": 4,
    "entityId": 15,
    "presetId": 1,
    "name": "Primary requisite",
    "active": true,
    "sort": 500,
    "code": null,
    "xmlId": null,
    "addressOnly": false,
    "createdAt": "2025-01-15T09:30:00+00:00",
    "updatedAt": "2026-03-20T14:00:00+00:00",
    "createdBy": 1,
    "modifyBy": 1,
    "rqName": "Acme LLC",
    "rqInn": "1234567890",
    "rqKpp": "123456789",
    "rqOgrn": "1234567890123",
    "rqOkpo": "12345678",
    "rqOkved": "62.01",
    "rqOktmo": null,
    "rqVatPayer": false,
    "rqCompanyName": "Acme",
    "rqCompanyFullName": "Acme Limited Liability Company",
    "rqDirector": "John Smith",
    "rqAccountant": "Anna Brown",
    "rqCeoName": null,
    "rqCeoWorkPos": null,
    "rqContact": null,
    "rqEmail": null,
    "rqPhone": null,
    "rqBaseDoc": "Charter"
  }
}
```

## Error response example

404 — requisite not found:

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

## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 404 | `ENTITY_NOT_FOUND` | No requisite with that ID found |
| 403 | `ACCESS_DENIED` | No access to the parent entity (contact/company) |
| 403 | `SCOPE_DENIED` | API key does not have the `crm` scope |
| 401 | `TOKEN_MISSING` | API key has no configured tokens |

Full list of common API errors — [Errors](/docs/errors).

## Known specifics

**The field set depends on the preset.** A requisite stores only the fields defined in its preset (`presetId`). For example, the "LLC" preset has `rqCompanyName`, `rqCompanyFullName`, `rqDirector`, while the "Individual" preset has `rqFirstName`, `rqLastName`, `rqSecondName`, etc. Preset fields that are not filled are returned as `null`.

**Schema fields — camelCase, custom — in the original case.** All Vibecode schema fields, including international preset fields `rqEdrpou`, `rqKbe`, `rqRegon` and rare service fields `rqIfns`, `rqUsrle`, are returned in camelCase. Filtering and sorting use the same name. Custom `UF_CRM_*` fields are returned in the original Bitrix24 case.

## See also

- [Requisite fields](/docs/entities/requisites/fields) — all possible fields
- [Update requisite](/docs/entities/requisites/update) — change values
- [Delete requisite](/docs/entities/requisites/delete) — delete a record
- [List requisites](/docs/entities/requisites/list) — search with filters
- [Limits and optimization](/docs/optimization) — rate limits