Troubleshoot
Last updated April 30th, 2026
The Knox Guard API uses the conventional HTTP response status codes to indicate the success or failure of a request. A 2XX response code indicates success, a 4XX response code indicates a client-side error, and a 5XX response code indicates a server-side error.
In addition, responses contain a JSON response body with more details about the operation. For example:
Standard HTTP error codes
The following table lists common HTTP status codes returned by the Knox Guard API:
| Code | Name | Description |
|---|---|---|
| 200 | Success | The request was successfully received. |
| 400 | Bad Request | The client has issued an invalid request. Verify your request (for example, check for validation errors in the request payload). |
| 401 | Unauthorized | Missing or expired authentication token. |
| 403 | Forbidden | The request has been authenticated, but the tenant or user doesn't have sufficient permissions to make the call. |
| 404 | Not Found | The requested resource doesn't exist. |
| 406 | Not Acceptable |
The client has requested a MIME type via the Accept header for a value that isn't supported by the server.
|
| 422 | Unprocessable Entity | The client has made a valid request, but the server can't process it. This is often returned for APIs when certain limits have been exceeded. |
| 429 | Too Many Requests | The client has exceeded the number of requests allowed for a given time window. |
| 500 | Internal Server Error | An unexpected error on the servers has occurred. These errors should be rare. |
| 501 | Not Implemented | The client request was valid and understood by the server, but the requested feature has yet to be implemented. These errors should be rare. |
Error response body
The error response body contains two properties:
| Property | Type | Description |
|---|---|---|
| result | String | SUCCESS/FAIL |
| error | Error | Error object |
The error object
Error responses include an error object, which has the following attributes:
| Property | Type | Description |
|---|---|---|
| code | String | A Knox Guard defined error code that serves as a more specific indicator of the error than the HTTP response code. |
| message | String | A description of the error, intended to aid developers in debugging the error response. |
| reason | String | A description of the error, intended to aid developers in debugging the error response. |
Knox Guard error codes
Knox Guard specifies the following custom error codes which provide more information than the standard HTTP error response codes. The table below lists the standard Knox Guard error codes and their descriptions:
| Code | Message | Description |
|---|---|---|
| 4010000 | AUTHORIZATION_FAIL | The API key is not valid or the restriction data does not match. |
| 4002102 | API_KEY_RESTRICTION_INVALID | The IP address or HTTP referer format is incorrect. |
| 4042101 | API_KEY_RESTRICTION_NOT_FOUND | The IP address or HTTP referer is empty. |
| 4040100 | USER_NOT_FOUND | There is no user linked to the API key. |
| 4040900 | TENANT_NOT_FOUND | There is no tenant linked to the API key. |
| 4000000 | RESOURCE_INVALID_PARAM | Argument is invalid. |
| 4001809 | LICENSE_IS_LACK | There are no additional licenses that can be activated. |
| 4040300 | DEVICE_NOT_FOUND | The specified device was not found. |
| 4000310 | DEVICE_STATE_INVALID | The operation is not permitted in the current state. |
| 4000316 | DEVICE_BULK_OPERATION_LIMIT_EXCEEDED | The bulk operation limit has been exceeded. |
| 4040400 | PROFILE_NOT_FOUND | Internal profile not found. |
| 4001807 | LICENSE_MAX_COUNT_REACHED | License max count reached. |
| 4001805 | LICENSE_NAME_ALREADY_EXISTS | License name already exists. |
| 5001804 | LICENSE_INTERNAL_SERVER_FAILED | Error communicating with the license server. |
| 4001813 | LICENSE_KEY_ALREADY_EXISTS_IN_OTHER_REGION | License key already registered to another region (EU/US). |
| 4001802 | LICENSE_MAX_TRIAL_LICENSE_COUNT_REACHED | Max trial license count reached. |
| 4041800 | LICENSE_NOT_FOUND | License not found. |
| 4001806 | LICENSE_DEVICE_MAPPING_FOUND | Device already registered with a license. |
| 4001812 | LICENSE_ALREADY_DELETED | License already deleted. |
| 4030102 | USER_IN_INVALID_STATE | User state is invalid. |
| 4030107 | USER_REJECTED_STATE | User is rejected by Samsung Admin. |
| 4030104 | USER_BLOCKED_STATE | User is blocked by Samsung Admin. |
| 4030106 | USER_PENDING_STATE | User is not approved yet. |
| 4120000 | PRECONDITION_FAILED_EXCEPTION | Customer doesn't have a SIM control configuration. |
On this page
Is this page helpful?