To configure document flow using the API, Saby has a basic set of steps:
- Authentication.
Any user session starts with authentication. During authentication, the user is passed a string with the session ID. This ID must be sent to the server when each API command is executed.
- Preparing documents for sending and uploading them to Saby.
Before sending the documents, you must prepare them. To do this, specify the signatory and the ID's of the participants in the document flow. If the document flow supposes to have service attachments, generate them. To get feedback you need to specify the ID's of the documents and their attachments. This can be done in a format that is set up in your information system.
- Signing and sending documents.
Each of the documents that you send to the counterparty must be signed with an electronic signature. You can sign documents both in your system and in Saby.
- Monitoring the status of outgoing and incoming documents.
You can control changes for outgoing and incoming documents. You can track the document status in the workflow using a set of events.
- Processing incoming documents.
Document flow regulations may require processing of incoming documents: verification, rejection, or approval. You can determine the need for processing based on the document status. Incoming documents can be processed both in your system and in Saby
- The generation of service documents.
Service documents can be generated in your information system, or automatically by the Saby server. If the service documents are generated automatically, the correct filling and format of the documents will be guaranteed to meet the requirements of the legislation and the document flow regulations. When generating documents independently, you need to track and make changes to the document format yourself. If the document does not match the required format, it will not be accepted by the server.
- Maintaining a local archive of documents.
Saby allows you to maintain a local copy of the archive of electronic documents. The archive will contain incoming, outgoing, and service documents, as well as files of electronic signatures. The document archive can be stored both in your information system and in Saby. Saby allows you to store them without a time limit.
We recommend using the standard integration option. You can also create your own version from the suggested stages.
Also Saby API allows you to:
- Reassign the document stage performer
- Cancel the document by agreement of the parties
- Delete documents
- Associate documents
- Visualize the documents
- Create a draft document using the link in your personal account
- Display the document card in the issuer's dashboard and register a new counterparty
License
The «Exchange with partners» and «Implementation of EDI» tariffs of «Electronic Document Flow» service.