canonical: https://jentic.com/apis/swaggerhub.bo-integration/swaggerhub-bo-integration

# Bo Integration 1С ДМС: загрузка корпоративных и индивидуальных договоров

Описание спецификации для сохранения в КСАСК "ProfITsoft" договора из 1С в статусе предложения и его заключения. The API exposes 7 endpoints.

## For AI agents

Programmatically сохранение договора, сохранение массива договоров. Covers 7 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Сохранение договора
- Заключение договора
- Создание запроса на расторжение договора
- Получение графика платежей по договору с распределениями для этапов оплаты
- Регистрация дополнительных соглашений к договорам ДМС

## Use cases

### Developer Tools Operations

Use the 1С ДМС: загрузка корпоративных и индивидуальных договоров to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including сохранение договора, сохранение массива договоров, заключение договора.

Example prompt: Call POST /bo/app/rest/api/contract/dmsImport to сохранение договора

### Automated dms Management

Automate dms operations by combining multiple 1С ДМС: загрузка корпоративных и индивидуальных договоров endpoints. Agents can сохранение массива договоров and then заключение договора in a single workflow.

Example prompt: Call POST /bo/app/rest/api/contracts/dmsImport to сохранение массива договоров, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call 1С ДМС: загрузка корпоративных и индивидуальных договоров endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'сохранение договора', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /bo/app/rest/api/contract/dmsImport | Сохранение договора |
| POST | /bo/app/rest/api/contracts/dmsImport | Сохранение массива договоров |
| POST | /bo/app/rest/api/contract/conclude/dms | Заключение договора |
| POST | /bo/app/rest/api/generalContract | Сохранение генерального договора |
| POST | /bo/app/rest/api/contract/cancellationRequest | Создание запроса на расторжение договора |
| GET | /bo/app/rest/payment/contractSchedulePremieListWithRepayments | Получение графика платежей по договору с распределениями для этапов оплаты |
| POST | /bo/app/rest/api/contract/additionalCondition | Регистрация дополнительных соглашений к договорам ДМС |

## Key resources

- **dms** — 1С ДМС: загрузка корпоративных и индивидуальных договоров

## Why Jentic

- **Setup:** Wiring this 1C DMS contract-import API by hand means mapping its bo/app/rest contract endpoints, formatting each import and conclusion payload, and handling retries yourself. Through Jentic you install once, import this API from the API Directory, and your agent calls it without you writing that plumbing.
- **Permission scoping:** The contract operations carry their target in the request body rather than a resource id in the URL path, so scope the agent to the operations it needs, such as importing contracts with POST /bo/app/rest/api/contract/dmsImport. You choose the allowed set, so submitting a cancellation request with POST /bo/app/rest/api/contract/cancellationRequest is not included unless you add it.
- **Credential handling:** This spec defines no authentication, so there is no credential to store. If you point it at a host that adds a key later, that key is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'import a corporate insurance contract' or 'conclude a DMS contract', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the 1С ДМС: загрузка корпоративных и индивидуальных договоров use?

The 1С ДМС: загрузка корпоративных и индивидуальных договоров uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I сохранение договора with the 1С ДМС: загрузка корпоративных и индивидуальных договоров?

Yes. Use the POST /bo/app/rest/api/contract/dmsImport endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the 1С ДМС: загрузка корпоративных и индивидуальных договоров?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I сохранение договора through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'сохранение договора'. Jentic returns the matching 1С ДМС: загрузка корпоративных и индивидуальных договоров operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the 1С ДМС: загрузка корпоративных и индивидуальных договоров have?

The 1С ДМС: загрузка корпоративных и индивидуальных договоров exposes 7 endpoints covering dms operations.

### Can I limit what my agent is allowed to do with the 1C DMS contract API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, and every operation carries its target in the request body rather than a URL path id, so you scope by operation. You can allow the agent to import contracts with POST /bo/app/rest/api/contract/dmsImport while leaving out other operations, so submitting a cancellation request with POST /bo/app/rest/api/contract/cancellationRequest stays blocked unless you add it. The spec defines no authentication, so there is no credential to hand over, and if a downstream host later requires a key your self-hosted instance stores it encrypted and injects it at execution time, keeping it out of the agent's context.