The API interface allows you to perform the Saby system actions in the familiar interface of your information system. Using Saby API, you can:
- log in to Saby;
- prepare the documents to be sent and import them to Saby. Saby can independently prepare documents for sending — specify the signatory, the IDs of the document workflow parties, and generate service documents. When importing documents to Saby, the IDs of documents and their attachments can be transmitted in a format that is understandable to your system;
- send outgoing documents to counterparties and track their status;
- generate service documents. Saby automatically creates all the necessary service documents. You just need to set up the processing and exporting of service documents in your information system;
- receive incoming documents from counterparties and approve them;
- maintain a local archive of documents.
How it works
The described features are the main stages of integration. Depending on the degree of integration, some of the steps will be performed by your system using API methods, and some in the Saby interface.
The distribution of functions between your information system and Saby can be either full or partial.
Saby will act only as an invisible channel for the transfer of documents between your system and counterparties.
In this case, all stages of document flow — uploading, sending documents, status monitoring, etc. — are performed in your system using API methods.
There are a lot of options for partial integration. The most popular scenario for sending outgoing documents to counterparties using an API:
- Create a source document in your system.
- Using the API interface, import the document to Saby.
- Open the document in Saby by clicking the link/button in your system.
- Send the document and monitor its status from the document window in Saby. The status of the document (sent/approved/rejected) is displayed in your system (if there is a technical possibility).
The incoming documents approved in Saby can be moved to your system using the API interface. And just as in the case of outgoing docs, it’s possible to implement a button/link to go to a legally binding document that will be stored in Saby.
The archive will be stored in Saby. If needed, it can be exported to a directory on the computer/server.
If this integration option suits you, consider a ready-made integration solution using the Saby Connect utility.
Where to start
- Register on sbis.ru. To log in, use a username/password or create a new user.
- Connect the «Exchange with counterparties» pricing plan of the «E-document Workflow» service.
- Configure your information system so that it calls API methods and processes the returned data.