...
Looking for the full detail of our APIs?
Get working code snippets in the language of your choice through our Slate documentation.
You’ll be up and running in no time with our clear focused getting-started guide. All you need to do is plug in your own API keys.
...
Integrating the solution
...
Step | Description |
1 | The customer server uploads a document to the contract.fit servers for analysis. This can follow, e.g., a bulk scan or processing an email inbox |
2 | Contract.fit processes the document. As part of this step, contract.fit uses third party services such as cloud OCR |
3 | Contract.fit informs the customer that the analysis has been done. If human intervention is required, the customer creates a review task for an operator |
4 | To enable SSO, the browser will request an access token to the identity provider of the customer (e.g., through Kerberos, SAML, or OAuth) |
5 | The operator reviews the document in his/her browser. This is an exception-based review, focusing only on areas where review is requested |
6 | The operator has the option to save intermediate work (e.g., before his lunch break) |
7 | The operator finalises his/her work. The output of the review is used to inform the feedback loop of contract.fit |
8 | Contract.fit sends the final result to the customer servers |
9 | Customer instructs contract.fit to delete the analysis. Only non-personal data required for statistics is retained |
Infrastructure set-up
Our infrastructure is set up according to the following scheme.
