Asyncronous
Document verifications are async. When you start a verification, you’ll receive theid along with a scheduled status.
When the job starts, the status will change to processing. Once the job is completed, the status will change to complete.
If a job fails for some reason, the status will change to failed.
Camber sends webhooks when a document verification has either completed or failed. You can then retrieve the verification result using the id.
Results
When a document verification is complete, you’ll receive adecision, confidence score, any issues and the extracted data.
Decision
Thedecision is the core output of a document verification. It lets you know whether the document was accepted or rejected. If Camber is unsure, it will return flagged. If a job fails, the decision will default to failed.
Confidence
Theconfidence score is between 0 and 100 and represents our confidence in the decision. It is not probability of acceptance.
Issues
Theissues are any issues that Camber found with the document. For example, if the document is expired, or the name on the document does not match the name in our system, it will be listed as an issue. Each document
has a list of issues that it can return, along with some universal issues.
Data
Thedata is the extracted data from the document. Each document type has a different set of data that it can return. For example, a tuberculosis test will return the date of the test, the type of test, and the result.