Document exchange, reporting and labelling
Document exchange services connect under Integrations. The general rules (kinds of connection, card statuses, Read only, disconnecting) are on the Connecting services page. How the agent asks before changes is described in Action confirmation.
The agent works with the rights of the employee or key you connected. A qualified signature held on a token is applied by you. 1C and MoySklad have their own pages: 1C and MoySklad.
Saby (SBIS)
Sending, receiving and signing documents. More on the integration page.
What the agent can do
Reads incoming and outgoing documents with attachments and statuses, checks whether a counterparty is on document exchange, and assembles a package for sending if the connection has write rights. It signs with the company's server certificate only on your direct command.
Show the incoming documents in @sbis that wait for our decision: counterparty, amount, date received. Do not sign anything.
Before you start
A Saby employee whose role opens the sections you need. If the profile holds several companies, decide whose documents the agent needs.
Steps
The Saby (SBIS) card has two ways. The main one:
Click Connect via Saby
Sign in at online.sbis.ru with the employee's login and password.
Pick the company and confirm access
If there are several companies, sign in to the one whose documents the agent needs and confirm consent to data access.
If signing in with the account does not suit you, under the button there is the Another way to connect line: the service key of your own application.
Open Connections to Saby
In your account at online.sbis.ru: «Настройки» → «Система» → «Безопасность» → «Подключения к Saby» (Settings, System, Security, Connections to Saby) and click the add button.
Fill in the application card
Any clear name and description will do, for example "Samreshuuu". Pick the application type. The external system address or IP field limits where Saby accepts authorization requests from; an empty field accepts them from any address.
Grant rights
Service access «Разрешен полностью» (fully allowed) or «С ограничением по правам» (limited by rights) with access to document exchange. Authorization type «по сервисному ключу» (by service key). Save.
Move three values into the form
«ID подключения» into App ID, «Защищенный ключ» (revealed with the eye icon) into App Secret, the service key from the «с авторизацией по сервисному ключу» line into Secret Key.
Permissions to grant
With Saby sign-in the agent gets the employee's rights: to leave it only document exchange, connect as an employee whose role opens only those sections. A service key's rights are set in the application card.
How to revoke access
Click Disconnect here. A service key application is deleted in «Подключения к Saby».
Troubleshooting
- The agent does not see another company's documents: a different company was picked at sign-in. Connect the right one through Add another.
- Missing permissions: the employee's or application's role does not open the section. Widen it in Saby.
Kontur.Diadoc
Sending, receiving and signing documents. More on the integration page.
What the agent can do
Reads the box's incoming and outgoing documents and prepares sending within the key's rights.
Before you start
An integrator account at integrations.kontur.ru: Diadoc API keys are issued on request at diadoc.ru/integrations/api, and a Kontur manager opens the account.
Steps
Take client_id and client_secret
Both values are in the integrator account. Paste them into Client ID and Client Secret.
Issue a refresh token
Pick clientMode "AuthorizationCode", tick the scopes openid, offline_access and Diadoc.PublicAPI and click to get a refresh token. Paste it into Refresh token.
Copy the box ID
Open the incoming documents and copy from the address bar the 32 characters between diadoc.kontur.ru/ and /Folder/Inbox into Box ID.
Limitations
The connection regularly swaps the refresh token by itself, and the previous one stops working at once. Do not paste the same token into another program: there it stops working after the first exchange.
How to revoke access
Click Disconnect here. The application and its keys live in Kontur's integrator account.
Troubleshooting
- No refresh token is issued: the offline_access scope is not ticked.
- Credentials not accepted after the same token went into another program: issue a new refresh token for this connection only.
Kontur.Extern
Electronic reporting: drafts, document flows, companies, certificates. More on the integration page.
What the agent can do
Works with your companies' reporting drafts and document flows.
Steps
Send a request
The «Отправить заявку» (send a request) form at kontur.ru/extern/api. A manager emails you a client_id and a link to issue a key.
Issue the key
Following the link to integrations.kontur.ru, click «Выпустить ключ» (issue key).
Fill in the form
client_id from the email into Client ID, the issued key into API Key.
Limitations
The key from the first email works only on the testkontur.ru test environment. A production key is issued the same way after a contract with Kontur.
How to revoke access
Click Disconnect here. The key is managed at integrations.kontur.ru.
Troubleshooting
- Reporting is not visible: a test key is connected. After the contract, issue a production one and click Re-enter credentials.
Kontur.Focus
Counterparty checks by INN and OGRN: company details, risks, monitoring. More on the integration page.
What the agent can do
Checks companies and sole proprietors by INN and OGRN before a deal.
Steps
Leave a request
At focus.kontur.ru/site/api click «Бесплатная консультация» (free consultation) and give the company INN. Ask for the «Реквизиты» method (/api3/req): without it requests are refused on rights.
Paste the key from the email
The key arrives by email to the contract address and is not shown anywhere in Focus. Paste it into API Key.
How to revoke access
Click Disconnect here. Kontur issues and closes the key under the contract.
Troubleshooting
- Refused on rights: the contract lacks the «Реквизиты» method. You can test the key at focus-api.kontur.ru/api3/req/userform.
Chestny ZNAK
Product labelling: marking codes, documents, product cards, stock. More on the integration page.
What the agent can do
Reads and checks marking codes and their statuses, documents, product cards and stock, and prepares lists for signing. Putting documents into circulation needs a qualified signature from your token, and you do that.
Before you start
- Participation in GIS MT: your product group must be listed in «Профиль» → «Данные участника» (Profile, Participant details). One INN, one account.
- A program with CryptoPro and your qualified signature to get the token.
Steps
Get a True API token
True API issues it, not the account: a program with CryptoPro takes a string to sign from True API (/auth/key), signs it with your qualified signature and receives the token in reply to /auth/simpleSignIn. This is how 1C and accounting systems that support labelling get it.
Paste the token
Paste the token into Auth Token. It is a long string of three parts separated by dots.
Limitations
- The «Сгенерировать токен» button in the GIS MT profile does not work: it issues a key for checks at the cash register, and True API does not accept it.
- A True API token lives for a limited time. When it expires the agent says so: issue a new one and update it in the connection.
How to revoke access
Click Disconnect here. The token stops working on its own when it expires.
Troubleshooting
- Credentials not accepted: the token expired. Issue a new one and click Re-enter credentials.
- No data for a product group: the group is not added to the participant profile.
PARUS 8 (integration service)
Exchange with PARUS 8 through the «Сервис интеграции с WEB API» application server. More on the integration page.
What the agent can do
Calls the operations you declared in the database's service functions.
Before you start
The «Сервис интеграции с WEB API» application server installed next to the PARUS 8 database: without it no request reaches the database.
Steps
Set up an exchange service
In the «Сервисы обмена» (exchange services) directory create a service and set its root URL.
Declare the functions
In the «Функции сервиса» (service functions) directory set an address, HTTP method and database handler for each operation.
Fill in the form
The application server address with its port into Server URL, the service root into Exchange service root.
Limitations
An address not declared in the service functions does not exist for the server: it answers 404.
How to revoke access
Click Disconnect here. Operations are removed from the service functions.
Troubleshooting
- Connecting fails: open the server address with the service root in a browser. A live exchange answers with a page showing the application server version and the service name.
HRlink HR document exchange
HR document exchange: documents, applications, employees. More on the integration page.
What the agent can do
Reads the employee and document registers and applications.
Before you start
An employee with the «Кадровик» (HR officer) role: other roles have the registers closed and no token option in the menu. Your own account address like company.hr-link.ru.
Steps
Issue a token
The initials icon at the top right → «Получить API-токен» (get API token) → copy. Paste it into API Token.
Enter the address and client ID
The account address into Server URL, the HRlink client identifier into Client ID: the GET /api/v2/currentUser call on your address returns it in the currentUser.clientUsers[].client.id field.
If HRlink gave you an integration token, fill in Master token and User for the master token instead of the HR officer's token: the agent then works on behalf of that user.
Limitations
The HR officer's token works for a limited period, after which it is issued again.
How to revoke access
Click Disconnect here.
Troubleshooting
- The registers refuse: the token was not issued under the «Кадровик» role.
- Wrong account: the shared portal.hr-link.ru does not fit your account, enter your own address.
Frequently asked questions
How do I connect Saby if signing in through Saby does not suit me?
Connect with the service key of your own application. In Saby: «Настройки» → «Система» → «Безопасность» → «Подключения к Saby», add an external application with the «по сервисному ключу» authorization type. Move three values into the Samreshuuu form: «ID подключения» into App ID, «Защищенный ключ» into App Secret, the service key into Secret Key.
Which token does Chestny ZNAK need?
A True API token issued against a qualified e-signature. The «Сгенерировать токен» button in the GIS MT profile does not work: it issues a key for checks at the cash register. A True API token lives for a limited time, after which you issue a new one and update it in the connection.
Does the agent sign documents in document exchange?
A qualified signature held on a token is applied by you. The agent reads documents and statuses and assembles a package for sending if the connection has write rights; it signs with the company's server certificate only on your direct command.
Where do I get Diadoc and Kontur.Extern keys?
Kontur issues API keys on request: for Diadoc at diadoc.ru/integrations/api, for Extern at kontur.ru/extern/api. A manager opens the integrator account, where the values are issued.
See also
Didn't find an answer? How to reach us