# Payer types

Methods: `sale.persontype.*`. Scope: `sale`.

## Operations

- [Create](./person-types/create.md): `POST /v1/person-types`
- [List](./person-types/list.md): `GET /v1/person-types`
- [Get](./person-types/get.md): `GET /v1/person-types/:id`
- [Update](./person-types/update.md): `PATCH /v1/person-types/:id`
- [Delete](./person-types/delete.md): `DELETE /v1/person-types/:id`
- [Search](./person-types/search.md): `POST /v1/person-types/search`
- [Fields](./person-types/fields.md): `GET /v1/person-types/fields`
- [Aggregate: Payer types](./person-types/aggregate.md): `POST /v1/person-types/aggregate`

## Usage notes

This dictionary is shared by CRM and the online store: payer types determine requisites, payment systems and order properties. Deactivation and deletion affect orders and invoices. CRM_CONTACT and CRM_COMPANY are protected: deletion returns 422 with the Bitrix24 message. Codes are unique; duplicates return 422. The cloud assigns the site lid; it is read-only.

Y/N flags accept and return booleans. Missing record: 404 ENTITY_NOT_FOUND. Business refusal: 422 with the Bitrix24 message. Empty POST: 400 MISSING_REQUIRED_FIELDS. A READONLY key cannot write (403). Lists support filter, select, sort, limit, offset; Bitrix24 pages contain 50 rows and V1 fetches more automatically when limit > 50.

`POST /v1/batch`, `POST /v1/person-types/batch`.