错误返回
更新时间：2025-08-21
错误返回格式
通用错误返回格式如下：
Plain Text
1{
2 "requestId": "<bce-request-id>",
3 "code":"<error-code>",
4 "message":"<error-message>",
5 "success":false
6 }LSS专用错误返回码
| 错误码 | 错误信息 | 描述 | HTTP状态码 |
|---|---|---|---|
| AccessDenied | You have no permission to the live streaming service | 不可以使用音视频直播服务，请联系工单开通 | 403 |
| UserOverdue | your account is overdue, please renew it | 用户账号欠费，请续费 | 403 |
| InvalidSession | Invalid session parameter | 创建流参数错误 | 400 |
| NoSuchSession | the requested session does not exist | 流不存在 | 404 |
| OperationNotPermitted | Invalid operation | 非法操作 | 403 |
| InvalidPreset | Invalid preset parameter | 创建模板参数错误 | 400 |
| DuplicatePreset | duplicate preset name | 模板名称已被使用 | 400 |
| NoSuchPreset | The requested preset does not exist | 模板不存在 | 404 |
| DeleteActiveResource | Preset is in use | 资源使用中，无法删除 | 403 |
| InvalidSecurityPolicy | Invalid security policy parameter | 更新模板参数错误 | 400 |
| DuplicateSecurityPolicy | duplicate security policy name | 安全策略名称已被使用 | 400 |
| NoSuchSecurityPolicy | No such security policy | 安全策略不存在 | 404 |
| SecurityPolicyInUse | security policy is used by some sessions | 安全策略使用中，无法更新 | 403 |
| InvalidNotification | Invalid notification parameter | 创建通知参数错误 | 400 |
| DuplicateNotification | duplicate notification name | 通知名称已被使用 | 400 |
| NoSuchNotification | notification does not exist | 通知不存在 | 404 |
| NotificatioInUse | notification is used by some sessions | 通知使用中，无法删除 | 403 |
通用错误返回码
| 错误返回码 | 错误消息 | 状态码 | 说明 |
|---|---|---|---|
| AccessDenied | Access denied. | 403 Forbidden | 无权限访问对应的资源。 |
| InappropriateJSON | The JSON you provided was well-formed and valid, but not appropriate for this operation. |
400 Bad Request |
请求中的JSON格式正确，但语义上不符合 要求。如缺少特定必需项，或值类型不匹配 等。出于兼容性考虑，对于所有无法识别 的项应直接忽略，不应该返回这个错误。 |
| InternalError | We encountered an internal error. Please try again. |
500 Internal Server Error |
所有未定义的其他错误。在有明确对应的 其他类型的错误时（包括通用的和服务自 定义的）不应该使用。 |
| InvalidAccessKeyId | The Access Key ID you provided does not exist in our records. | 403 Forbidden | Access Key ID不存在。 |
| InvalidHTTPAuthHeader | The Access Key ID you provided does not exist in our records. | 400 Bad Request | Authorization头域格式错误。 |
| InvalidHTTPRequest | There was an error in the body of your HTTP request. |
400 Bad Request |
HTTP body格式错误。例如不符合特定的 Encoding等。 |
| InvalidURI | Could not parse the specified URI. | 400 Bad Request |
URI形式不正确。例如一些服务定义的关键 词不匹配等。对于ID不匹配的问题，应定义 更加具体的错误码，如NoSuchKey。 |
| MalformedJSON | The JSON you provided was not well-formed. | 400 Bad Request | JSON格式不合法。 |
| InvalidVersion | The API version specified was invalid. | 404 Not Found | URI的版本号不合法。 |
| OptInRequired | A subscription for the service is required. | 403 Forbidden | 没有开通对应的服务。 |
| PreconditionFailed | The specified If-Match header doesn’t match the ETag header. | 412 Precondition Failed | 详见Etag。 |
| RequestExpired | Request has expired. Timestamp date is <Data> . | 400 Bad Request | 请求超时。<Data>要改成x-bce-date。若 请求中只有Date，需将Date转成datetime。 |
| IdempotentParameterMismatch | The request uses the same client token as a previous, but non-identical request. | 403 Forbidden | clientToken对应的API参数不一样。 |
| SignatureDoesNotMatch | The request signature we calculated does not match the signature you provided. Check your Secret Access Key and signing method. Consult the service documentation for details. |
400 Bad Request |
Authorization头域中附带的签名和服务端 验证不一致。 |
| 错误返回码 | 错误消息 | 状态码 | 说明 |
|---|---|---|---|
| AccessDenied | Access denied. | 403 Forbidden | 无权限访问对应的资源。 |
| InappropriateJSON | The JSON you provided was well-formed and valid, but not appropriate forthis operation. | 400 Bad Request | 请求中的JSON格式正确，但语义上不符合要求。如缺少特定必需项，或值类型不匹配等。出于兼容性考虑，对于所有无法识别的项应直接忽略，不应该返回这个错误。 |
| InternalError | We encountered an internal error. Please try again. | 500 Internal Server Error | 所有未定义的其他错误。在有明确对应的其他类型的错误时（包括通用的和服务自定义的）不应该使用。 |
| InvalidAccessKeyId | The Access Key ID you provided doesnot exist in our records. | 403 Forbidden | Access Key ID不存在。 |
| InvalidHTTPAuthHeader | The Access Key ID you provided does notexist in our records. | 400 BadRequest | Authorization头域格式错误。 |
| InvalidHTTPRequest | There was an error in the body of your HTTP request. | 400 Bad Request | HTTP body格式错误。例如不符合特定的Encoding等。 |
| InvalidURI | Could not parse the specified URI. | 400 Bad Request | URI形式不正确。例如一些服务定义的关键词不匹配等。对于ID不匹配的问题，应定义更加具体的错误码，如NoSuchKey。 |
| MalformedJSON | The JSON you provided was not well-formed. | 400 BadRequest | JSON格式不合法。 |
| InvalidVersion | The API version specified was invalid. | 404 NotFound | URI的版本号不合法。 |
| OptInRequired | A subscription for the service is required. | 403 Forbidden | 没有开通对应的服务。 |
| PreconditionFailed | The specified If-Match header doesn’tmatch the ETag header. | 412 PreconditionFailed | 详见Etag。 |
| RequestExpired | Request has expired. Timestamp date is <Data>. | 400 BadRequest | 请求超时。<Data>要改成x-bce-date。若请求中只有Date，需将Date转成datetime。 |
| IdempotentParameterMismatch | The request uses the same client token asa previous, but non-identical request. | 403 Forbidden | clientToken对应的API参数不一样。 |
| SignatureDoesNotMatch | The request signature we calculated does not match the signature you provided. Check yourSecret Access Key and signing method. Consultthe service documentation for details. | 400 Bad Request | Authorization头域中附带的签名和服务端验证不一致。 |