Skip to main content
Set these environment variables using the credentials provided by Trelent. See Authentication for details. Typical turnaround is 60–120 seconds, with processing time continually improving.

Three requests

This cURL outline shows the flow with abbreviated responses. Copy the returned token into ACCESS_TOKEN and the detection ID into DETECTION_ID before sending the next request.

Run the flow

The Python example uses requests; the TypeScript example uses Node.js with built-in fetch. Both stop polling on success or failure and allow up to 40 minutes before timing out.
Display the score and detailed reasoning in your platform for human review of high-risk documents. A higher score means a higher likelihood of fraud, but does not guarantee fraud. Humans should always review high-risk cases. Some completed detections have a null score and an authoritative finding instead. See Get a detection for result fields, and Start a detection for supported inputs and request errors. For sample allowances, see Billing. To try requests interactively, download an API collection.