Authenticity Verification: start task
POST/api/technology/experimental/authenticity-verification
Please note that Authenticity Verification is an experimental feature.
It is under development and may change in the future.
Start an Authenticity Verification task for a media file.
Authenticity Verification features
The Authenticity Verification endpoint supports the following independent operations:
- Deepfake Detection
- Audio Manipulation Detection
- Replay Attack Detection
Be default, all operations are performed, and they are billed together as one Authenticity
Verification task. It is possible to specify the list of requested operations (deepfake_detection
,
audio_manipulation_detection
, replay_attack_detection
) to save computational resources.
Features of all the operations
- Multi-channel media files are supported.
- For each channel an independent operation's result is produced.
- Processing can be limited to a specific time segment in the media file with query parameters.
Deepfake Detection specific features
- If there is less than 3 seconds of audio in a processed channel (or time segment), the score will
be empty (i.e.
null
).
Audio Manipulation Detection specific features
- Under the hood, the technology analyzes overlapping segments of 400 ms. By default, additional
logic is applied to the raw segments, joining adjacent suspicious segments into one to improve the
usability of the results. To obtain the raw segmentation instead, use the
raw_segmentation=True
query parameter.
Request
Responses
- 202
- 400
- 403
- 413
- 422
- 429
- 507
Authenticity Verification task was accepted. Follow the Location
header to poll for the task state.
Response Headers
⚠️ Deprecated - use Location
header instead.
/api/technology/authenticity-verification/123e4567-e89b-12d3-a456-426614174000
A URL the client should poll for task state and result.
/api/technology/authenticity-verification/123e4567-e89b-12d3-a456-426614174000
Request payload data was invalid and could not be parsed.
Request is forbidden.
The request entity (payload) size exceeds the allowed limit.
Error during validation of request payload data occurred.
Request rate limit exceeded.
The request may be retried after a while. The following response headers may be checked for details: retry-after
, x-ratelimit-limit
, x-ratelimit-remaining
, x-ratelimit-reset
.
Response Headers
Header indicates how long the user agent should wait before making a follow-up request.
Size of the current rate limiting window.
Remaining number of requests in the current rate limiting window.
Time at which the current rate limiting window resets (in UTC epoch).
The storage is full and cannot accept any data.