All Documents
Current Document
Content is empty
If you don't find the content you expect, please try another search term
Content is empty
If you don't find the content you expect, please try another search term
Last updated：2026-03-18 14:19:31
If the API response contains an error field, it means the API call has failed. A typical error response looks like the following:
JSON Format
{
"requestid": "7106664e-bce9-4871-b5df-9cf6e25ce142",
"error": {
"type": "sender",
"code": "InvalidParameterValue",
"message": "Invalid `InstanceID` parameter value, length must be 36 characters."
}
}Field | Type | Description |
|---|---|---|
| String | Unique ID of the failed request. Use this when submitting support tickets. |
| String | Error source type. |
| String | Error code. Use this to identify the specific error category. |
| String | Human-readable description of the error with specific details. |
Note: A small number of APIs may return error responses in a different format due to compatibility between legacy and new service versions. Please handle these cases accordingly.
The table below lists all common error codes returned by the Kingsoft Cloud Monitor API. For error codes specific to individual API operations, refer to the Error Codes section of each API's documentation page.
HTTP Status | Error Code | Error Message | Description & Resolution |
|---|---|---|---|
400 |
| The request is missing parameter | One or more required request parameters are absent or invalid. Check your request and ensure all required fields are included. |
400 |
| The Request is missing Signature Parameter | The request was rejected because no valid signature was provided. Ensure the |
400 |
| Access Key is Missing | The request was rejected because no Access Key was provided. Include a valid |
400 |
| The request is missing timestamp parameter | The request was rejected because the signature timestamp is absent. Include a valid |
400 |
| No such namespace | The specified |
400 |
| Request information is too large | The single request is attempting to pull too much data. To resolve: reduce the |
400 |
| The action or version is not valid for this web service | The |
400 |
| Invalid Timestamp. Pls in 15mins | The signature request timestamp is invalid. Ensure the request timestamp is within 15 minutes of the current server time. |
400 |
| Invalid Accesskey | The provided Access Key is invalid. Check that you are using the correct key for your account. |
400 |
| The Signature is not matched | The |
400 |
| The region is unavailable for the openapi | The specified region is not supported by this API. Refer to the Region List for supported regions. |
401 |
| Without access to call Inner Openapi | Regular users do not have permission to access internal OpenAPI endpoints. |
401 |
| The Account ID is invalid | The Account ID is invalid. Check your account configuration and environment settings. |
403 |
| lack of policy to [monitor:getmetricstatistics] the resources[] | The sub-account does not have the required permissions. The primary account must grant |
403 |
| [xxx(namespace)] product does not belong to this user | The |
404 |
| Invalid service | The request was rejected because the referenced service does not exist. |
404 |
| No such name for 'metrics' | The specified |
409 |
| Request was rejected because it referenced an 'InnerApi' that does not exist | The request was rejected because the API call rate has exceeded the rate limit threshold. Reduce the request frequency and implement retry logic with backoff. |
412 |
| Request would have succeeded, but DryRun flag is set | The request would have succeeded but was not executed because the |
500 |
| Internal Service is unavailable because of time out | An internal service error or timeout occurred. The service is temporarily unavailable. Retry the request after a short delay, and contact support if the issue persists. |
Pure Mode