Keyword Spotting: start task
POST/api/technology/keyword-spotting
Start Keyword Spotting task from a media file.
Keyword Spotting features
- Multi-channel media files are supported.
- Language must be specified in RFC 5646 format.
- Processing can be limited to a specific time segment with query parameters.
- Result contains a list of matches from all channels, sorted by channel number and time stamps.
Request
Responses
- 202
- 400
- 403
- 413
- 422
- 429
- 507
Keyword Spotting task was accepted. Follow the Location
header to poll for the task state.
Response Headers
⚠️ Deprecated - use Location
header instead.
/api/technology/keyword-spotting/123e4567-e89b-12d3-a456-426614174000
A URL the client should poll for task state and result.
/api/technology/keyword-spotting/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.
Maximum number of requests which is allowed in the currently used rate limiting window.
Remaining number of requests in the currently used rate limiting window.
Time at which the current rate limiting window resets (in UTC epoch).
The storage is full and cannot accept any data.