Speaker Diarization: start task
POST/api/technology/speaker-diarization
Start a Speaker Diarization task for a media file.
Speaker Diarization features
- Multi-channel media files are supported.
- For each channel an independent Speaker Diarization result is produced.
- Speaker Diarization can be configured by two mutually exclusive parameters
max_speakers
andtotal speakers
, therefore, only one of them can be used at a time. - The parameter
max_speakers
is the upper boundary for the number of speakers that are believed to be speaking in the media file. - The parameter
total_speakers
is the exact number of speakers that are believed to be speaking in the media file. If set, the Speaker Diarization result will contain this number of speakers. - Processing can be limited to a specific time segment in the media file with query parameters.
Request
Responses
- 202
- 400
- 403
- 413
- 422
- 429
- 507
Speaker Diarization task was accepted. Follow the X-Location
header to poll for the task state.
Response Headers
A URL the client should poll for task state and result.
/api/technology/speaker-diarization/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.