Common errors
This page lists the error and status codes you may encounter when using the Real-Time STT RESTful APIs. In case of other errors, contact Agora technical support.
Response status codes
When calling Real-Time STT RESTful APIs, you may receive the following HTTP status codes:
200for a successful request.- Not
200for a failed request. In this case, check themessage,code, andreasonfields in the response body to figure out what has happened. Thereasonfield might be absent.
Response examples
When a request fails, you may receive the following response:
-
Only
message: -
Only
codeandreason:
Status codes
| Code | Description |
|---|---|
200 | The request is successful. To call acquire, record tokenName. To call start, record taskId and map it to tokenName. |
201 | The service is already running. Do not repeat the start request with the same tokenName. |
206 | No host in the channel sent a stream during the transcribing process. |
400 | The server cannot process the request due to malformed request syntax, or the Real-Time STT service is not enabled. |
401 | Unauthorized (incorrect Customer ID/Customer Secret). |
404 | The requested resource could not be found. |
409 | The task has already been started. |
500 | Internal server error. |
504 | Internal communication error. |
Error messages and codes
Message
"the product name does not match with builderToken": The acquiredbuildTokenhas an issue. Callacquireagain."resourceId reaches out the limited time interval!": ThebuildTokenexpired after the 5-minute validity period. Make sure to usetokenNameto start the service within 5 minutes after callingacquire. When the task has been created successfully, save thetokenName, since it will be used to callquery,update, andstop."invalid_appid!": The Real-Time STT service is not enabled for your app. Enable it in the Console or send a request to Agora technical support."body schema check fail, ...": Thestartorupdatebody is wrong."..."describes the reason of failure. Always caused by parameter mismatch or exceeding the range. Recheck the request body."The taskId does not match with builderToken.": Check whytaskIdandtokenNamedo not match."The task is not found": The task has been terminated."The task has been started, current status is STARTED, taskId is ...": The task has been started. RecordtaskIdand map it totokenName.
Error code
1: Internal server error when callingstart. Contact Agora technical support if you need more support.2: Invalid parameter. Possible reasons:- Wrong data type.
- Wrong spelling. All parameters are case sensitive.
- Parameter value is out of range.
- Mandatory parameter is missing.
6: Internal server error when callingstart. Contact Agora technical support if you need more support.20: Caused by processing timeout. Retry the same call with the back-off strategy, after 3 and 6 seconds.23: Internal server error when callingstart. Contact Agora technical support if you need more support.49: Caused by repeatedstartrequests with the sametokenNameor repeatedstoprequests with the sametokenNameandtaskId.53:taskidandbuildtokendo not match.62: If you receive this error when callingacquire, the Real-Time STT service is not enabled for your App ID. Enable it in the Console or contact Agora technical support. If you receive this error when callingstart, it means the service is not started due to a network issue.404: The task has been terminated when callingqueryorstop.501: Internal server error when callingstart. Contact Agora technical support if you need more support.502: Internal server error when callingstart. Contact Agora technical support if you need more support.504: Internal server error when callingstart. Contact Agora technical support if you need more support.1001: Failed to parsetokenName. Callacquireto get a newtokenName.1003: The App ID ortaskIddoes not matchtokenName. Ensure that the App ID ortaskIdmatchestokenNamein each Real-Time STT task.
Notes
- The
resourceIdandtokenNameparameters are the same. In some cases,builderTokenalso meanstokenName. - Contact Agora technical support if you encounter an error not mentioned in this documentation.