Document Upload

Document Sacn and Upload to Votiro server

• The user interface (UI) initiates a request to the '/scan' POST API, which is exposed by the wrapper doc-scan service.
• Internally, the wrapper service then triggers a call to the Votiro async upload POST API to commence scanning the document.
• Upon receiving a response from the Votiro upload API (which includes the document_id), this information is promptly relayed back to the UI for further handling.

Check for document scan status

• UI makes a sync call to the doc-scan wrapper service “/status” endpoint
• Wrapper service internally polls for the scan status by invoking the Votiro “/status” endpoint for every 1 second until it receives any one of these statuses “Done” / “Blocked” / “Error” / “NotExist”
• Wrapper API would max poll 45 times, if the scan is still not completed, then it would throw an appropriate error message back to UI.

Get file and upload to Azure Blob

• UI uploads the files to Azure storage by invoking “/upload” wrapper api.
• Wrapper api internally invokes Votiro “/download” api and download the files for the given document id.
• Wrapper API internally invokes “/upload” api and streams the response received from Votiro download api directly to azure storage.
• Upon upload to Azure storage, wrapper api would return the appropriate file upload status back to UI.

Upload to OTCS

• Upload the document via the OTCS document upload topic after successful Votiro scanning
• Map the response to the document ID for storage under the respective entity.