How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Trusona ATO Protect Verification API

REST API to create and read identity verifications: send a hosted scan link by SMS or email, read overall risk, per-verifier checks, risk scores, scanned documents and the devices seen during the verification. Also offers an encrypted variant where responses are returned under a caller-supplied JWK. Bearer JWT auth.

This API exposes 13 operations across 11 paths, organized into 6 resource areas, and defines 27 schemas. It is described by OpenAPI 3.1.0, at version 2.2.0.

Requests are made against a single base URL, https://authcloud.trusona.net.

13 operations 11 paths 27 schemas 10 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.2.0
Base URL
https://authcloud.trusona.net
Authentication
HTTP Bearer
Resource Areas
6

Authentication & Security 1

Trusona ATO Protect Verification API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 13

Across 11 paths, the API surfaces 13 operations — 10 GET, 3 POST. They span 6 resource areas: Verifications, Messages, Encrypted Verifications, Risk Scores, Documents, Devices. Each is listed below with its method, path, parameters, and response codes.

Verifications 3
GET
/api/v1/verifications
Get verifications since a specific time or verification ID
getVerifications 4 params → 200400401500
POST
/api/v1/verifications
Create a new verification
createVerification body → 201400
GET
/api/v1/verifications/{verificationId}
Get verification by ID
getVerification 1 param → 200404
Messages 3
GET
/api/v1/verifications/{verificationId}/messages
Get all messages for a verification
getMessages 1 param → 200404
POST
/api/v1/verifications/{verificationId}/messages
Add a message to a verification
createMessage 1 param body → 201400404410422429
GET
/api/v1/verifications/{verificationId}/messages/{verificationMessageId}
Get a verification's message by ID
getMessage 2 params → 200404
Encrypted Verifications 3
POST
/api/v1/encrypted/verifications
Create a new verification with encrypted response
createEncryptedVerification body → 201400401422
GET
/api/v1/encrypted/verifications/{verificationId}
Get an encrypted verification by ID
getEncryptedVerification 1 param → 200401404
GET
/api/v1/encrypted/verifications/{verificationId}/document
Get an encrypted document by verification ID
getEncryptedDocument 1 param → 200401404410
Risk Scores 1
GET
/api/v1/verifications/{verificationId}/risk_scores
Get all scores for a verification
getRiskScores 1 param → 200404
Documents 2
GET
/api/v1/verifications/{verificationId}/document
Get the verification's document
getDocument 1 param → 200404410
GET
/api/v1/verifications/{verificationId}/document/scanned_images
Get the scanned image of the document
getScannedImages 1 param → 200404410
Devices 1
GET
/api/v1/verifications/{verificationId}/devices
Get all devices for a verification
getDevices 1 param → 200404

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are VerificationDevice (37 properties), ScanResponse (33 properties), VerificationResponse (27 properties), VerificationSummary (12 properties). Each schema is shown below with its type and property counts.

CreateVerificationDto
object
6 properties 1 required
RequestedCopyMessage
1 required
RequestedDmvVerifier
Request a DMV (AAMVA) verification.
1 required
RequestedEmailMessage
Send an email message to the provided email address.
2 required
RequestedLexisNexisVerifier
Request a LexisNexis verification.
1 required
RequestedMessage
object
1 property 1 required
RequestedMnoVerifier
Request an MNO (mobile network operator) verification.
1 required
RequestedSmsMessage
Send an SMS message to the provided phone number.
1 required
RequestedTrustedSmsMessage
Send a trusted SMS with SIM swap detection to the provided phone number.
1 required
RequestedVerifier
object
1 property 1 required
VerificationSubject
object
Subject identity information supplied by the API consumer for matching against the scanned document.
6 properties
Matches
object
Verifier match results. The shape depends on the verifier type: DMV matches include fields like firstName, lastName, dateOfBirth, documentNumber, etc. MNO matc…
RiskScore
object
12 properties
ServiceNowAttachment
A ServiceNow ticket attachment.
2 required
TicketNumberAttachment
A generic ticket number attachment.
2 required
VerificationAttachment
object
1 property 1 required
VerificationDevice
object
37 properties 7 required
VerificationHistory
object
10 properties
VerificationMessage
object
6 properties
VerificationResponse
object
27 properties 1 required
VerificationSummary
object
12 properties 3 required
WorkspaceCallbackAttachment
2 required
CreateEncryptedVerificationDto
object
7 properties 1 required
EncryptedVerificationResponse
object
3 properties
ScanResponse
object
Parsed data from a scanned identity document.
33 properties
IdentityImage
object
2 properties
EncryptedDocumentResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trusona-verification-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Trusona ATO Protect Verification API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.