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

Keyword Spotting task was accepted. Follow the Location header to poll for the task state.

Response Headers

X-Location
⚠️ Deprecated - use Location header instead.
Example: /api/technology/keyword-spotting/123e4567-e89b-12d3-a456-426614174000
Location
A URL the client should poll for task state and result.
Example: /api/technology/keyword-spotting/123e4567-e89b-12d3-a456-426614174000

400

Request payload data was invalid and could not be parsed.

403

Request is forbidden.

413

The request entity (payload) size exceeds the allowed limit.

422

Error during validation of request payload data occurred.

429

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

retry-after

Header indicates how long the user agent should wait before making a follow-up request.

x-ratelimit-limit

Maximum number of requests which is allowed in the currently used rate limiting window.

x-ratelimit-remaining

Remaining number of requests in the currently used rate limiting window.

x-ratelimit-reset

Time at which the current rate limiting window resets (in UTC epoch).

507

The storage is full and cannot accept any data.