Verifications
Verifications are performed on audios to analyze and measure certain characteristics, which vary depending on the type of verification.
The generic verifications endpoint provides a unified view of all the different types, displaying only their common fields.
Access: To manage a verification, you must have access to its space.
Isolation: Verifications can only interact with resources inside its space.
Model: The analysis of the relevant characteristics is powered by a specific version of a verification model.
Score: Confidence in a positive result is represented by the score.
Types
Fields
The UUID of the verification. Is unique.
uuid
00000000-0000-0000-0000-000000000000
The handle of the verification. Is unique.
verification-a
The alias of the verification.
Verification A
The type of the verification.
VerificationType (string)
Possible values: [identity
, authenticity
, message
]
authenticity
The state of the verification.
VerificationState (string)
Possible values: [performing
, performed
, performedWithoutScore
, error
]
performed
The model of the verification.
default/v1
audio
object | null
required
The audio of the verification.
The handle of the audio. Is unique.
audio-a
The alias of the audio.
Audio A
The state of the audio.
AudioState (string)
Possible values: [avaitingFile
, available
, notAvailable
]
available
The score of the verification.
float
Possible values: <= 1
0.85
The date and time when the verification was created.
date-time
2023-01-01T00:00:00.000000Z
The date and time when the verification was performed.
date-time
2023-01-01T00:00:00.000000Z
{
"id": "00000000-0000-0000-0000-000000000000",
"handle": "verification-a",
"alias": "Verification A",
"type": "authenticity",
"state": "performed",
"model": "default/v1",
"audio": {
"handle": "audio-a",
"alias": "Audio A",
"state": "available"
},
"score": 0.85,
"createdAt": "2023-01-01T00:00:00.000000Z",
"performedAt": "2023-01-01T00:00:00.000000Z"
}