In conjunction with proper HTTP status codes, non-2xx responses will have the following schema:
1 2 3 4{ code: string; // "INVALID_KEY_FORMAT" message: string; // "Invalid key format" }
Each 400 Bad Request response will be accompanied by an error code containing more information. The following tables lists all possible error codes, what they mean, and what you can do to address each one:
| Error code | Description |
|---|---|
| KEY_TOO_SHORT | The provided key needs to be more than one character. |
| KEY_TOO_LONG | The provided key has exceeded the maximum 500 characters. |
| INVALID_KEY | The provided key does not match the regex: /^(?!\s+$)[a-zA-Z0-9:._\s-#]+$/ |
| NOT_FOUND | The specified key does not exist. |
| Error code | Description |
|---|---|
| MAX_SIZE | The provided value has exceeded the maximum size limit. |
| MAX_DEPTH | The provided value has exceeded the maximum object depth (32) limit. |
| Error code | Description |
|---|---|
| INVALID_FILTER_CONDITION | The specified condition is not supported for filters. |
| INVALID_FILTER_VALUES | The specified number of values are not supported by the given condition. |
| LIST_QUERY_LIMIT_EXCEEDED | Limit for list query should be below 100. |
| QUERY_WHERE_INVALID | KVS queries should contain only a single "where" clause. |
| QUERY_WHERE_FIELD_INVALID | The specified field is not supported for filters. |
Rate this page: