Партнерское API СБИС

https://github.com/x020/sbis_reg_api
Admin
Партнерское API СБИС предоставляет интерфейс для интеграции внешних CRM-систем с биллинговой...
Tokens:50,135
Snippets:135
Trust Score:4.2
Update:4 months ago
Show doc for...
Tokens:
Raw
### Billing.GetHistory JSON-RPC Request Examples

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Integraciya-s-vneshnimi-sistemami/Billing-GetHistory.md

Examples of how to call the Billing.GetHistory method using JSON-RPC. These requests demonstrate different parameter configurations, including filtering by actions.

```json
{
    "jsonrpc": "2.0",
    "method": "Billing.GetHistory",
    "params": {
        "PointSale": "0240",
        "DateFrom": "2018-11-26",
        "DateTo": "2018-11-28",
        "SubPoints": false,
        "NavigationKey": null
    },
    "protocol": 2,
    "id": 0
}
```

```json
{
    "jsonrpc": "2.0",
    "method": "Billing.GetHistory",
    "params": {
        "PointSale": "0240",
        "DateFrom": "2018-11-26",
        "DateTo": "2018-11-28",
        "SubPoints": false,
        "Actions": ["Активность контрагента", "Реквизиты и контакты"],
        "NavigationKey": null
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Billing.GetHistory JavaScript Browser Console Examples

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Integraciya-s-vneshnimi-sistemami/Billing-GetHistory.md

Examples of how to invoke the Billing.GetHistory method from a browser's console using requirejs and SbisService. These snippets show setting up the service endpoint and calling the method with different parameters.

```javascript
requirejs(['Types/source'], function(blo){
    new blo.SbisService({
        endpoint: {
            contract: 'Billing',
            address: '/partner_api/service/sbis-rpc-service300.dll'
        }
    }).call(
        'GetHistory', 
        {
            "PointSale": "0240",
            "DateFrom": "2018-11-26",
            "DateTo": "2018-11-28",
            "SubPoints": false,
            "NavigationKey": null
        }
    );
});
```

```javascript
requirejs(['Types/source'], function(blo){
    new blo.SbisService({
        endpoint: {
            contract: 'Billing',
            address: '/partner_api/service/sbis-rpc-service300.dll'
        }
    }).call(
        'GetHistory', 
        {
            "PointSale": "0240",
            "DateFrom": "2018-11-26",
            "DateTo": "2018-11-28",
            "SubPoints": false,
            "Actions": ["Активность контрагента", "Реквизиты и контакты"],
            "NavigationKey": null
        }
    );
});
```

--------------------------------

### Contractor.InfoByID API Request Example (JSON-RPC)

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Contractor-InfoByID.md

An example of a JSON-RPC request to the Contractor.InfoByID API. This request is used to fetch detailed information for a specific contractor identified by 'ContractorID'.

```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.InfoByID",
    "params": {
        "ContractorID": 1126971809
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Account.SendInvite JSON Request Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Podklyuchenie-k-online.sbis.ru/Account-SendInvite.md

Example JSON payload for the Account.SendInvite API method. This demonstrates the structure for sending an invitation with a specific account ID, invitation letter ID, and immediate sending preference.

```JSON
{
    "jsonrpc": "2.0",
    "method": "Account.SendInvite",
    "params": {
        "AccountID": 578320,
        "LetterID": "1cf18a9f-4f5a-43fd-8589-df41bf33edde",
        "SendAtOnce": true
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Account.PrepareCabinet JSON RPC Request

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Podklyuchenie-k-online.sbis.ru/Account-PrepareCabinet.md

Example JSON RPC request to the Account.PrepareCabinet method. This request prepares the cabinet for a specific account by providing its AccountID.

```json
{
    "jsonrpc": "2.0",
    "method": "Account.PrepareCabinet",
    "params": {
        "AccountID": 112697
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### License.Activate JSON-RPC Request Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-licenziyami/License-Activate.md

This snippet demonstrates a typical JSON-RPC request to activate a license using the License.Activate method. It includes the necessary parameters like LicenseID and ActivationDate.

```json
{
    "jsonrpc": "2.0",
    "method": "License.Activate",
    "params": {
        "LicenseID": "4f40fed3-2bc4-4bc2-bedb-08623e4ded6f",
        "ActivationDate": null
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Example Serialized RecordSet in JSON-RPC v2.0 (protocol: 2)

Source: https://github.com/x020/sbis_reg_api/blob/main/partner-api-data.md

Provides a concrete example of a serialized RecordSet for protocol version 2, demonstrating the structure with sample data for ServiceID, ServiceCount, and ServiceCost.

```JSON
{
    "s": [
        {"n": "ServiceID", "t": "Строка"}, 
        {"n": "ServiceCount","t": "Числоцелое"},
        {"n":"ServiceCost","t":"Деньги"}
    ],
    "d": [
        ["EOpSBISfrmUo", 1,4700.00],
        ["EOpNI", 2, 1200.00],
        ["EO_null_online", 1, 500.00]
    ]
}
```

--------------------------------

### Account.InfoByID JSON Request Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Account-InfoByID-1.md

This is an example of a JSON-RPC request to the Account.InfoByID method. It requires the AccountID as a parameter to retrieve specific account information.

```json
{
    "jsonrpc": "2.0",
    "method": "Account.InfoByID",
    "params": {
        "AccountID": 730157
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Account.KktLicenseSet API Request Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-kassami-OFD/Account-KktLicenseSet.md

This JSON snippet demonstrates a typical request to the Account.KktLicenseSet method. It includes the necessary parameters like the JSON-RPC version, method name, parameters (AccountID), protocol version, and an ID for the request.

```json
{
    "jsonrpc": "2.0",
    "method": "Account.KktLicenseSet",
    "params": {
        "AccountID": 4363913
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Partner.StaffList JSON-RPC Request

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Zakreplenie-klientov/Partner-StaffList.md

An example of a JSON-RPC request to the Partner.StaffList method. This specific example requests staff information for all partners within region code '78'. The 'PartnerCode' is set to null to indicate no specific partner is being queried.

```json
{
    "jsonrpc": "2.0",
    "method": "Partner.StaffList",
    "params": {
        "RegionCode": "78",
        "PartnerCode": null
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### KKT.AttachToLicense Example JSON RPC Call

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-kassami-OFD/KKT-AttachToLicense.md

Demonstrates how to call the KKT.AttachToLicense method using JSON RPC. This involves specifying the method name and providing parameters such as AccountID, LicenseID, INN, and KktRegID within the 'params' object. The method is used to attach a cash register to a license, effectively extending its validity. Note that the 'Data.s' object contains placeholder string types, while 'Data.d' contains actual example values.

```json
{
    "jsonrpc": "2.0",
    "method": "KKT.AttachToLicense",
    "params": {
        "Data": {
            "s": {
                "AccountID": "Числоцелое",
                "LicenseID": "Строка",
                "INN": "Строка",
                "KktRegID": "Строка"
            },
            "d": {
                "AccountID": 5050330,
                "LicenseID": "3cbb8ade-1ae0-4259-8024-28e9b7af0f49",
                "INN": "7717778943",
                "KktRegID": "0000000505033001"
            }
        }
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Example License.InfoByID API Call (JSON)

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-licenziyami/License-InfoByID.md

This snippet demonstrates a sample JSON request to the License.InfoByID method, used to retrieve information about a specific license extension. It includes the necessary JSON-RPC version, method name, parameters, protocol version, and an ID.

```JSON
{
    "jsonrpc": "2.0",
    "method": "License.InfoByID",
    "params": {
        "LicenseID": "4f40fed3-2bc4-4bc2-bedb-08623e4ded6f"
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Find or Create Contractor and Get Account Info

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Podklyuchenie-k-online.sbis.ru/Podklyuchenie-k-online.sbis.ru.md

This snippet covers finding or creating a contractor and then retrieving information about the accounts associated with that contractor. It's a foundational step in the connection process.

```markdown
[Contractor.FindOrCreate](../Rabota-s-klientami/Contractor-FindOrCreate.md) (Реквизиты_контрагента)
[Contractor.InfoByID](../Rabota-s-klientami/Contractor-InfoByID.md) (ID_контрагента)
```

--------------------------------

### Example JSON RPC Call for Account.ReassignByLogin

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Zakreplenie-klientov/Account-ReassignByLogin.md

This snippet demonstrates how to call the Account.ReassignByLogin method using JSON RPC. It includes the necessary parameters: AccountID, UserLogin, and an optional Reason for the reassignment.

```json
{
    "jsonrpc": "2.0",
    "method": "Account.ReassignByLogin",
    "params": {
        "AccountID": 730157,
        "UserLogin": "teterin.sa",
        "Reason": "Увольнение сотрудника"
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Example JSON RPC Call for Account License Management

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-licenziyami/Account-LicenseSet.md

Demonstrates a JSON RPC request to the Account.LicenseSet method. This call is used to manage account licenses, likely for setting or retrieving license information. It requires the AccountID as a parameter.

```JSON
{
    "jsonrpc": "2.0",
    "method": "Account.LicenseSet",
    "params": {
        "AccountID": 4363913
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Contractor.FindByINNandKPP JSON Request Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Contractor-FindByINNandKPP.md

This JSON object demonstrates a sample request to the Contractor.FindByINNandKPP method. It includes the required parameters INN and KPP, along with other standard JSON-RPC fields. The KPP parameter is optional and should be null for individual entrepreneurs.

```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.FindByINNandKPP",
    "params": {
        "INN": "631919298912",
        "KPP": null
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Inspection.AvailableList API Call Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-gosorganami/Inspection-AvailableList.md

This JSON snippet demonstrates how to make a call to the Inspection.AvailableList method. It includes the necessary parameters such as ContractorID, InspectionType, and Region to specify the desired inspections.

```json
{
    "jsonrpc": "2.0",
    "method": "Inspection.AvailableList",
    "params": {
        "ContractorID": 1126971809,
        "InspectionType": 1,
        "Region": "76"
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Contractor.FindOrCreate JSON RPC Call Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Contractor-FindOrCreate.md

This snippet demonstrates a typical JSON RPC request to the Contractor.FindOrCreate method. It includes the 'jsonrpc', 'method', 'params' (with ContractorData), 'protocol', and 'id' fields.

```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.FindOrCreate",
    "params": {
        "ContractorData": {
            "s": {
                "INN": "Строка",
                "KPP": "Строка",
                "Name": "Строка"
            },
            "d": {
                "INN": "6449058159",
                "KPP": "644901001",
                "Name": "ЕВРО-ЗАПЧАСТЬ, ООО"
            }
        }
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Contractor.CreateWithAccount JSON RPC Request

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Contractor-CreateWithAccount.md

Example JSON RPC request for the Contractor.CreateWithAccount method. It includes contractor data (INN, KPP, Name) and a flag indicating if a new account is required. The response will contain AccountID and ContractorID.

```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.CreateWithAccount",
    "params": {
        "ContractorData": {
            "s": {
                "INN": "Строка",
                "KPP": "Строка",
                "Name": "Строка"
            },
            "d": {
                "INN": "7820331115",
                "KPP": "782001001",
                "Name": "\"Лентракт\", ООО"
            }
        },
        "NewAccountRequired": true
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Account.ContactData Method Call Example (JSON-RPC)

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Account-ContactData.md

This snippet demonstrates the JSON-RPC request format for the Account.ContactData method. It specifies the method to call, the parameters required (AccountID), and other standard JSON-RPC fields.

```json
{
    "jsonrpc": "2.0",
    "method": "Account.ContactData",
    "params": {
        "AccountID": 730157
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Example JSON-RPC Call for Contractor.ReassignByLogin

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Zakreplenie-klientov/Contractor-ReassignByLogin.md

This JSON snippet demonstrates a typical request to the Contractor.ReassignByLogin method. It includes the method name, parameters for contractor ID, user login, and the reason for reassignment. The method returns true on success or an error.

```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.ReassignByLogin",
    "params": {
        "ContractorID": 14000472,
        "UserLogin": "efremovaok",
        "Reason": "Первичное закрепление"
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Prepare Client Cabinet for Temporary Login

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Podklyuchenie-k-online.sbis.ru/Podklyuchenie-k-online.sbis.ru.md

This method prepares a client's cabinet on online.sbis.ru for login using a temporary login, which matches the account identifier. This is one of the options for client onboarding.

```markdown
[Account.PrepareCabinet](Account-PrepareCabinet.md) (ID_аккаунта);
```

--------------------------------

### Contractor.InspectionList API Request Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-gosorganami/Contractor-InspectionList.md

Example JSON-RPC request to the Contractor.InspectionList method. It requires a ContractorID as a parameter to fetch the relevant inspection data.

```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.InspectionList",
    "params": {
        "ContractorID": 500512351
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Billing: New Invitation and Client Creation

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Podklyuchenie-k-online.sbis.ru/Podklyuchenie-k-online.sbis.ru.md

This section describes using the Billing service for new invitations and direct client creation. It highlights considerations for existing accounts and how to associate accounts and organizations with a specific department.

```markdown
[Биллинг.НовоеПриглашение](Billing-NovoePriglashenie.md)
[Биллинг.СоздатьКлиента](Billing-SozdatKlienta.md)
```

--------------------------------

### Account.AddContractor API Request Example (JSON)

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Account-AddContractor.md

This is an example JSON request payload for the Account.AddContractor API method. It includes the AccountID and ContractorData required to add or manage a contractor.

```json
{
    "jsonrpc": "2.0",
    "method": "Account.AddContractor",
    "params": {
        "AccountID": 43907,
        "ContractorData": {
            "s": {
                "INN": "Строка",
                "KPP": "Строка",
                "Name": "Строка"
            },
            "d": {
                "INN": "631919298912",
                "KPP": null,
                "Name": "Богданов Виктор Анатольевич, ИП"
            }
        }
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### License.AvailableServices

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Prais-deystvuyushchih-uslug/License-AvailableServices.md

Fetches a list of available services for a given region, including their names, prices, and descriptions.

```APIDOC
## POST /x020/sbis_reg_api

### Description
This method returns information about services that can be subscribed to (prices may vary depending on the region).

### Method
POST

### Endpoint
/x020/sbis_reg_api

### Parameters
#### Request Body
- **jsonrpc** (string) - Required - JSON RPC version.
- **method** (string) - Required - The method to call, in this case, "License.AvailableServices".
- **params** (object) - Required - Parameters for the method.
  - **RegionCode** (string) - Required - The two-digit region code of the organization ordering the services.
- **protocol** (integer) - Required - The protocol version.
- **id** (integer) - Required - The request ID.

### Request Example
```json
{
    "jsonrpc": "2.0",
    "method": "License.AvailableServices",
    "params": {
        "RegionCode": "76"
    },
    "protocol": 2,
    "id": 0
}
```

### Response
#### Success Response (200)
- **Nomenclature** (string) - String identifier of the service (referred to as ServiceID in other methods of this API).
- **Name** (string) - Short name of the service.
- **FullName** (string) - Full name of the service.
- **Price** (string) - Price for 1 unit of this service type.
- **Description** (string) - Description of this service.
- **IsTariff** (boolean) - Indicates if this service is a tariff or can be used as a tariff.

#### Response Example
```json
{
  "result": [
    {
      "Nomenclature": "SRV001",
      "Name": "Service A",
      "FullName": "Full Name of Service A",
      "Price": "100.00",
      "Description": "Description for Service A",
      "IsTariff": true
    },
    {
      "Nomenclature": "SRV002",
      "Name": "Service B",
      "FullName": "Full Name of Service B",
      "Price": "150.50",
      "Description": "Description for Service B",
      "IsTariff": false
    }
  ]
}
```
```

--------------------------------

### POST /License.Activate

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-licenziyami/License-Activate.md

Activates a license if possible, otherwise returns an error describing the reason for refusal.

```APIDOC
## POST /License.Activate

### Description
Activates a license if possible, otherwise returns an error describing the reason for refusal.

### Method
POST

### Endpoint
/License.Activate

### Parameters
#### Request Body
- **LicenseID** (string (UUID)) - Required - Identifier of the license
- **ActivationDate** (Date) - Optional - The start date of the license. This parameter can be useful if you need to activate a license retroactively. The difference between the current date and the date passed in this parameter cannot exceed 30 days. If a null value is passed, the current date is used.

### Request Example
```json
{
    "jsonrpc": "2.0",
    "method": "License.Activate",
    "params": {
        "LicenseID": "4f40fed3-2bc4-4bc2-bedb-08623e4ded6f",
        "ActivationDate": null
    },
    "protocol": 2,
    "id": 0
}
```

### Response
#### Success Response (200)
- **ServiceSet** (List of records) - Set of services included in the license (including cost)
- **LicenseCost** (Monetary) - The cost of the license (all services included in it) with discounts applied

#### Response Example
```json
{
    "jsonrpc": "2.0",
    "result": {
        "ServiceSet": [
            {
                "ServiceID": "service123",
                "ServiceCount": 5,
                "ServiceCost": "100.00"
            }
        ],
        "LicenseCost": "500.00"
    },
    "id": 0
}
```

#### Error Response
- **Error** (object) - Contains error code and message
- **error.code** (integer) - Error code
- **error.message** (string) - Description of the error

#### Error Response Example
```json
{
    "jsonrpc": "2.0",
    "error": {
        "code": -32602,
        "message": "Invalid parameters"
    },
    "id": 0
}
```
```

--------------------------------

### Contractor.AttachToInspection API Call Example (JSON)

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-gosorganami/Contractor-AttachToInspection.md

An example JSON request body for the Contractor.AttachToInspection API method. This method is used to attach a submission direction to a specified inspection for a contractor. It requires ContractorID, SedType, InspectionCode, and optionally InspectionExtraCode.

```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.AttachToInspection",
    "params": {
        "ContractorID": 500512351,
        "SedType": 2,
        "InspectionCode": "000-010",
        "InspectionExtraCode": null
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Example JSON Request for License.AvailableServices

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Prais-deystvuyushchih-uslug/License-AvailableServices.md

Demonstrates the structure of a JSON-RPC request to the License.AvailableServices method. It specifies the method to call, parameters (including the region code), protocol version, and a request ID. This format is common for interacting with JSON-RPC based APIs.

```json
{
    "jsonrpc": "2.0",
    "method": "License.AvailableServices",
    "params": {
        "RegionCode": "76"
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Get Account Licenses

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-licenziyami/Account-LicenseSet.md

Retrieves license information for a given account ID.

```APIDOC
## GET /x020/sbis_reg_api/Account.LicenseSet

### Description
Retrieves license information for a given account ID.

### Method
GET

### Endpoint
/x020/sbis_reg_api/Account.LicenseSet

### Parameters
#### Query Parameters
- **AccountID** (integer) - Required - The identifier of the account.
```

--------------------------------

### NodeJS HTTP Request Example

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Primery-ispolzovaniya-API/Primer-ispolzovaniya-partnerskogo-API-na-NodeJS.md

Этот пример демонстрирует, как отправлять HTTP POST запросы с JSON-RPC данными в NodeJS. Он включает в себя настройку заголовков, сериализацию параметров и обработку ответов. Зависит от встроенного модуля 'http'.

```javascript
let http = require('http');

let login = "petr-test";
let password = "petr-test*12";

function invoke(url, method, params, sid) {
   let promise = new Promise(function (resolve, reject) {
      let postOptions = {
         method: "POST",
         headers: {
            "Content-Type": "application/json-rpc; charset=utf-8",
            "Accept": "application/json-rpc"
         }
      };

      let postData = JSON.stringify({
         "jsonrpc": "2.0",
         "method": method,
         "params": params,
         "protocol": 2,
         "id": 0
      });

      if (sid) {
         postOptions.headers["X-SBISSessionID"] = sid;
      }

      let postRequest = http.request(url, postOptions, function (res) {
         res.setEncoding("utf8");
         res.on("data", function (chunk) {
            let result = JSON.parse(chunk).result;
            resolve(result);
         });
      });
      postRequest.write(postData);
      postRequest.end();
   });

   return promise;
}

function getSID(login, password) {
   let promise = new Promise(function (resolve, reject) {
      let method = "СБИС.Аутентифицировать";
      let params = {
         "Логин": login,
         "Пароль": password
      };

      invoke('http://fix-reg.tensor.ru/auth/service/', method, params).then(function (result) {
         resolve(result);
      });
   });

   return promise;
}

getSID(login, password).then(function (sid) {
   let method = "Billing.GetHistory";
   let params = {
      "DateFrom": '2018-12-25',
      "DateTo": '2018-12-25',
      "PointSale": null,
      "SubPoints": false,
      "NavigationKey": null
   };
   invoke('http://fix-reg.tensor.ru/partner_api/service/', method, params, sid).then(function (result) {
      console.log(result);
   });
});
```

--------------------------------

### KKT.ActivatedList API Call Example (JSON)

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-kassami-OFD/KKT-ActivatedList.md

This JSON snippet demonstrates a typical request to the KKT.ActivatedList method. It includes parameters for the date range (StartDay, FinishDay) and an optional OfficeCode. The 'params.Data.d' field contains the actual values for the query.

```json
{
    "jsonrpc": "2.0",
    "method": "KKT.ActivatedList",
    "params": {
        "Data": {
            "s": {
                "StartDay": "Дата",
                "FinishDay": "Дата",
                "OfficeCode": "Строка"
            },
            "d": {
                "StartDay": "2018-01-21",
                "FinishDay": "2018-01-27",
                "OfficeCode": "1350"
            }
        }
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Account.InfoByID JSON-RPC Request

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Account-InfoByID-2.md

This snippet shows an example of a JSON-RPC request to the Account.InfoByID method. It includes the AccountID and LicenseID as parameters.

```json
{
    "jsonrpc": "2.0",
    "method": "Account.InfoByID",
    "params": {
        "AccountID": 730157,
        "LicenseID": "8b3bcf72-3324-411d-87ee-dece612ce7e3"
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Account.PrepareCabinet

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Podklyuchenie-k-online.sbis.ru/Account-PrepareCabinet.md

Prepares the personal scheme for a given account on online.sbis.ru and sends an invitation email if an email address is provided.

```APIDOC
## POST /api/account/preparecabinet

### Description
Prepares the personal cabinet for a given account on online.sbis.ru by populating its data. If the account has an email address, an invitation for registration is sent to that address. The invitation can be used to complete registration on online.sbis.ru. The invitation is sent asynchronously, and successful completion of the method does not guarantee email delivery.

### Method
POST

### Endpoint
/api/account/preparecabinet

### Parameters
#### Request Body
- **AccountID** (integer) - Required - The identifier of the account.

### Request Example
```json
{
    "jsonrpc": "2.0",
    "method": "Account.PrepareCabinet",
    "params": {
        "AccountID": 112697
    },
    "protocol": 2,
    "id": 0
}
```

### Response
#### Success Response (200)
- **result** (boolean) - Returns `true` if both data population and invitation creation were successful. Returns `false` if only data population was successful (e.g., no email address was provided). An exception is thrown if data population fails.

#### Response Example
```json
{
    "jsonrpc": "2.0",
    "result": true,
    "id": 0
}
```
```

--------------------------------

### Call Contractor.ContactData API

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Contractor-ContactData.md

Example JSON-RPC request to the Contractor.ContactData method, specifying the ContractorID to retrieve contact details.

```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.ContactData",
    "params": {
        "ContractorID": 730157
    },
    "protocol": 2,
    "id": 0
}
```

--------------------------------

### Python API Client for Partner API

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Primery-ispolzovaniya-API/Primer-ispolzovaniya-partnerskogo-API-na-Python.md

This Python code defines functions to interact with a partner API. It includes a generic `invoke` function for making JSON-RPC calls, a `login` function for authentication, and a `get_history` function to retrieve data based on date ranges. It requires the `requests` library for making HTTP requests.

```python
import json
import requests
from datetime import date


def invoke(method: str, params: dict, auth_sid) -> dict:
    """Вызов метода"""
    payload = {
        "jsonrpc": "2.0",
        "method": method,
        "params": params,
        "protocol": 2,
        "id": 0
    }
    headers = {
        'Host': 'fix-reg.tensor.ru',
        'Content-Type': 'application/json-rpc; charset=utf-8',
        'Accept': 'application/json-rpc'
    }

    if auth_sid:
        headers['X-SBISSessionID'] = auth_sid
        url = 'https://fix-reg.tensor.ru/partner_api/service/'
    else:
        url = 'https://fix-reg.tensor.ru/auth/service/'

    r = requests.post(url, headers=headers, data=json.dumps(payload))

    return json.loads(r.text)


def login(user_name, pwd) -> str:
    """Авторизация"""
    return invoke('САП.Аутентифицировать', {"login": user_name, "password": pwd}, None)['result']


def get_history(sid, date_from: date, date_to: date, nav_key=None, point_sale=None, subpoints=False) -> dict:
    """Получение изменений"""
    params = {'DateFrom': date_from.strftime('%Y-%m-%d'),
              'DateTo': date_to.strftime('%Y-%m-%d'),
              'PointSale': point_sale,
              'SubPoints':subpoints,
              'NavigationKey': nav_key}
    return invoke('Billing.GetHistory', params, sid)['result']


if __name__ == '__main__':
    sid = login('petr-test', 'petr-test*12')
    res = get_history(sid, date.today(), date.today())
    for record in res['d']:
        print(record)
```

--------------------------------

### Partner.StaffList

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Zakreplenie-klientov/Partner-StaffList.md

Retrieves a list of partners and their employees. You can filter by region code or partner code, or get information for the current partner.

```APIDOC
## POST /x020/sbis_reg_api

### Description
This method allows you to get brief information about partners and employees who make up the staff of these partners. If you need to get data for all partners whose offices are located in a particular region, you should specify only the first parameter, and pass a null value as the partner code. If you want to get information about a specific partner, you need to specify only the second parameter, and pass a null value as the region code. If neither parameter is specified, the method will return information about the current partner (i.e., the partner whose employee account the method was called under).

### Method
POST

### Endpoint
/x020/sbis_reg_api

### Parameters
#### Request Body
- **jsonrpc** (string) - Required - Specifies the JSON-RPC protocol version.
- **method** (string) - Required - The name of the method to call (e.g., "Partner.StaffList").
- **params** (object) - Required - An object containing the parameters for the method.
  - **RegionCode** (string) - Optional - The two-digit code of the region for which partner information is requested.
  - **PartnerCode** (string) - Optional - The four- or five-digit code of the partner for which information is requested.
- **protocol** (number) - Required - The protocol version.
- **id** (number) - Required - A unique identifier for the request.

### Request Example
```json
{
    "jsonrpc": "2.0",
    "method": "Partner.StaffList",
    "params": {
        "RegionCode": "78",
        "PartnerCode": null
    },
    "protocol": 2,
    "id": 0
}
```

### Response
#### Success Response (200)
- **jsonrpc** (string) - The JSON-RPC protocol version.
- **result** (object) - The result of the method call.
  - **RegionCode** (string) - The code of the region where the partner's office is located.
  - **RegionName** (string) - The name of that region.
  - **PartnerCode** (string) - The partner's code.
  - **PartnerName** (string) - The partner's name.
  - **EmployeeList** (array) - A list of employee records for the partner.
    - **EmployeeID** (integer) - The employee's identifier.
    - **EmployeeName** (string) - The employee's full name.
- **id** (number) - The identifier of the request.

#### Response Example
```json
{
  "jsonrpc": "2.0",
  "result": [
    {
      "RegionCode": "78",
      "RegionName": "Санкт-Петербург",
      "PartnerCode": "1234",
      "PartnerName": "ООО Образец",
      "EmployeeList": [
        {
          "EmployeeID": 1,
          "EmployeeName": "Иванов Иван Иванович"
        }
      ]
    }
  ],
  "id": 0
}
```
```

--------------------------------

### GET /Contractor/InspectionList

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-gosorganami/Contractor-InspectionList.md

Fetches the list of inspections for a specific contractor, including tax inspections, pension funds, and other government bodies.

```APIDOC
## GET /Contractor/InspectionList

### Description
Retrieves a list of inspections and the contractor's status in them for a given contractor.

### Method
POST

### Endpoint
/x020/sbis_reg_api

### Parameters
#### Request Body
- **jsonrpc** (string) - Required - JSON RPC version
- **method** (string) - Required - Method name: "Contractor.InspectionList"
- **params** (object) - Required - Parameters for the method
  - **ContractorID** (integer) - Required - Identifier of the contractor
- **protocol** (integer) - Required - Protocol version
- **id** (integer) - Required - Request ID

### Request Example
```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.InspectionList",
    "params": {
        "ContractorID": 500512351
    },
    "protocol": 2,
    "id": 0
}
```

### Response
#### Success Response (200)
- **TaxInspections** (object) - Information about tax inspections
- **PensionFunds** (object) - Information about pension funds
- **GovStatOrgans** (object) - Information about state statistics bodies
- **FSS** (object) - Information about FSS
- **FSRAR** (object) - Information about FSRAR
- **RPN** (object) - Information about RPN

Each object in this set has the following format:
- **ContractorIDAtInspection** (string) - Contractor registration number in PF, FSS, OKPO, IRUC identifier, FSRAR
- **InspectionList** (array of objects) - List of inspections of a certain type for which reporting directions have been added for the contractor

Each object in the nested list InspectionList has the following format:
- **Code** (string) - Inspection code
- **ExtraCode** (string) - Additional inspection code
- **SedType** (integer) - Inspection type (1 – NI, 2 – PF, 3 – TOGS, 4 – FSS, 7 – RPN, 9 – FSRAR)
- **Name** (string) - Official name of the inspection
- **RegistrationState** (integer) - Registration status (0 – no certificates, 1 – not registered, 2 – not all certificates registered, 3 – registered, 4 – no agreement with PFR, 5 – registration in progress, 6 – registration error, 7 – inspection not used, 8 – registered but last registration is in progress, 9 – registered but last registration has an error)
- **ReportDirectionID** (string) - Reporting direction identifier
- **PFRAgreementDate** (datetime) - PFR agreement date
- **PFRAgreementNumber** (string) - PFR agreement number

#### Response Example
```json
{
    "jsonrpc": "2.0",
    "result": {
        "TaxInspections": {
            "ContractorIDAtInspection": "12345",
            "InspectionList": [
                {
                    "Code": "01",
                    "ExtraCode": "01",
                    "SedType": 1,
                    "Name": "Tax Inspection 1",
                    "RegistrationState": 3,
                    "ReportDirectionID": "RD123",
                    "PFRAgreementDate": "2023-01-01T10:00:00Z",
                    "PFRAgreementNumber": "AGR-001"
                }
            ]
        },
        "PensionFunds": {
            "ContractorIDAtInspection": "67890",
            "InspectionList": []
        }
    },
    "id": 0
}
```
```

--------------------------------

### GET /Contractor.InfoByID

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Rabota-s-klientami/Contractor-InfoByID.md

Retrieves detailed information about a contractor by their unique ID. The response includes various attributes of the contractor and their associated accounts.

```APIDOC
## GET /Contractor.InfoByID

### Description
Retrieves detailed information about a contractor by their unique ID. The response includes various attributes of the contractor and their associated accounts.

### Method
GET

### Endpoint
/Contractor.InfoByID

### Parameters
#### Query Parameters
- **ContractorID** (integer) - Required - The unique identifier of the contractor.

### Request Example
```json
{
    "jsonrpc": "2.0",
    "method": "Contractor.InfoByID",
    "params": {
        "ContractorID": 1126971809
    },
    "protocol": 2,
    "id": 0
}
```

### Response
#### Success Response (200)
- **INN** (string) - The INN of the contractor.
- **KPP** (string) - The KPP of the contractor.
- **Name** (string) - The name of the contractor.
- **RealAddress** (string) - The actual address of the contractor.
- **LegalAddress** (string) - The legal address of the contractor.
- **OGRN** (string) - The OGRN of the legal entity or individual entrepreneur.
- **EmailAddress** (string) - Indicates the presence of email addresses for the contractor.
- **PhoneNumber** (string) - Indicates the presence of phone numbers for the contractor.
- **Representative** (string) - Indicates the presence of representatives for the contractor.
- **UserName** (string) - The username of the manager assigned to this contractor.
- **PartnerName** (string) - The name of the division to which this contractor is assigned.
- **OfficeCode** (string) - The code of the division to which this contractor is assigned.
- **RegionName** (string) - The name of the contractor's region.
- **BillingURL** (string) - A link to the contractor in Billing.
- **AccountList** (array of objects) - A list of accounts that include this contractor at the time of the call. See below for account attributes.

#### Account List Format
- **AccountID** (integer) - The ID of the account.
- **Name** (string) - The name of the account.
- **TariffPlan** (string) - The tariff plan of the current license for this account.
- **EDO** (integer) - Indicator of the contractor's connection to Electronic Document Management (EDO) in this account (0: not connected, 1: connected, 2: connected but EDO is prohibited for this contractor in this account).
- **ELO** (integer) - Indicator of the contractor's connection to Electronic Invoicing (ELO) in this account (0: not connected, 1: connected, 2: connected but ELO is prohibited for this contractor in this account).
- **UserName** (string) - The username of the manager assigned to this account.
- **PartnerName** (string) - The name of the division to which this account is assigned.
- **OfficeCode** (string) - The code of the division to which this account is assigned.
- **RegionName** (string) - The name of the region where the division is located.
- **CustomerUB** (boolean) - Whether the contractor is a UB (Authorized Accounting) client. True if the client is an UB client, False otherwise.

#### Response Example
```json
{
    "jsonrpc": "2.0",
    "result": {
        "INN": "7701000000",
        "KPP": "770301001",
        "Name": "Example Contractor",
        "RealAddress": "123 Main St, Moscow",
        "LegalAddress": "456 Business Ave, Moscow",
        "OGRN": "1027700000000",
        "EmailAddress": "info@example.com",
        "PhoneNumber": "+74951234567",
        "Representative": "John Doe",
        "UserName": "manager1",
        "PartnerName": "Sales",
        "OfficeCode": "MOW",
        "RegionName": "Moscow",
        "BillingURL": "https://billing.example.com/contractors/1126971809",
        "AccountList": [
            {
                "AccountID": 1,
                "Name": "Account Alpha",
                "TariffPlan": "Standard",
                "EDO": 1,
                "ELO": 0,
                "UserName": "manager1",
                "PartnerName": "Sales",
                "OfficeCode": "MOW",
                "RegionName": "Moscow",
                "CustomerUB": false
            }
        ]
    },
    "protocol": 2,
    "id": 0
}
```

### Error Handling
If a contractor with the specified ID is not found in Billing, the method will return an error.
```

--------------------------------

### Account.ReassignByID JSON-RPC Request

Source: https://github.com/x020/sbis_reg_api/blob/main/API-metody-dlya-vzaimodeystviya/Zakreplenie-klientov/Account-ReassignByID.md

Example JSON-RPC request to reassign an account by its ID. It specifies the account ID, the new user ID, and the reason for reassignment.

```json
{
    "jsonrpc": "2.0",
    "method": "Account.ReassignByID",
    "params": {
        "AccountID": 730157,
        "UserID": 3056,
        "Reason": "Увольнение сотрудника"
    },
    "protocol": 2,
    "id": 0
}
```
Tokens:
Raw