Get a detection
Read one detection and its result.
Poll this operation until status is COMPLETED or FAILED. The status
field always shows the durable record. The verdict field comes from the
workflow history, which expires after the retention period, so an old
COMPLETED detection can have verdict: null.
score is null when one check determined the document verification result alone. The
authoritative object then carries the document check finding.
A FAILED detection gives the reason in failure_code and
failure_message.
Scope: DocumentVerification:detections:get
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
The detection record, with the verdict if it exists.
The durable record plus, once completed, the workflow result.
QUEUED, RUNNING, COMPLETED, or FAILED.
QUEUED, RUNNING, COMPLETED, FAILED The fraud score, normally 0 to 100. A higher score means a higher likelihood of fraud, but does not guarantee fraud. Humans should always review high-risk cases. Null while the detection runs, and null when one check determined the document verification result alone.
The batch that holds this detection, if one exists.
Where the API keeps the document.
A sentence that explains failure_code.
The reason for a FAILED status. Null in all other states.
Facts that the pipeline found in the document, such as qr_present.
Set if one check determined the document verification result alone. The agent does not run in that case, so verdict and score are both null.
The result of the analysis. Null while the detection runs, and null again after the workflow history expires.
Why the analysis agent failed.
The agent run, for support requests.