All ThingSpace Location Services API resources use this set of status codes in responses.
| HTTP Status | Error Code | Message | Explanation and Suggested Action |
|---|---|---|---|
| HTTP Status400 | Error CodeINVALID_PARAMETER | MessageUnable to Cancel | Explanation and Suggested ActionAll/Partial request already completed “some or all device location request are completed” |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Invalid JSON |
Explanation and Suggested Action invalid JSON |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Device not found |
Explanation and Suggested Action Could not find devices specified by user |
| HTTP Status 400 |
Error Code CACHE_UNAVAILABLE |
Message Location cache has no data for this device |
Explanation and Suggested Action Verify the device ID, or set cacheMode=1 or 2 to request current location information |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Conflicting device list |
Explanation and Suggested Action Set allDevice to true OR provide an exclusion list of devices, but not both |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Consent check failed |
Explanation and Suggested Action The requested device is excluded from location services. You can send a POST /consents request to allow the device to be located |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Ownership or MDN validation failed |
Explanation and Suggested Action A device in the request does not belong to the specified account. Verify the device identifiers and MDNs and then retry the request |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message UWS verification failure (Could not find account {account}) |
Explanation and Suggested Action Verify the account number that you are using and then resend the request |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message UWS verification failure (The Session has expired.) |
Explanation and Suggested Action The VZ-M2M-Token has expired. Use a POST /session/login request to get a new token |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Device type check failed |
Explanation and Suggested Action The specified device is not an IoT device and is not eligible for location services |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Invalid account name |
Explanation and Suggested Action The account name in the request was not found. Verify the spelling of the account name and retry the request |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Unregistered account |
Explanation and Suggested Action The account in the request is not registered for Device Location Services |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Invalid accuracy mode |
Explanation and Suggested Action Verify currently supported accuracy modes |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Invalid cache mode |
Explanation and Suggested Action Specify 0, 1, or 2 for the cacheMode |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Empty device list |
Explanation and Suggested Action There were no devices in deviceList. Add devices to deviceList and resend the request |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Per request max devices exceeded |
Explanation and Suggested Action The request includes more than 10,000 devices. Reduce the number of entries in deviceList and resend the request |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Duplicate devices |
Explanation and Suggested Action A device appears twice in deviceList. Remove any duplicate entries and resend the request |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Input Binding Error |
Explanation and Suggested Action JSON format error |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Invalid device kind. Valid kinds are IMEI, MEID or ESN |
Explanation and Suggested Action The device kind was not recognized. Use IMEI, MEID or ESN |
| HTTP Status 400 |
Error Code INVALID_PARAMETER |
Message Invalid device ID format |
Explanation and Suggested Action The value of the Identifier element was not in the format required by the Kind element. Set the Identifier element to a value that is in the format required by the Kind element, and then resend the request |
| HTTP Status 400 |
Error Code INTERNAL_ERROR |
Message Failed to get location |
Explanation and Suggested Action Failed to retrieve device location. Retry the request |
| HTTP Status 400 |
Error Code INTERNAL_ERROR |
Message Fail to verify device |
Explanation and Suggested Action Could not verify that the device is a Verizon device |
| HTTP Status 400 |
Error Code PARAMETER_ERROR |
Message Ownership or MDN validation failed |
Explanation and Suggested Action The device does not belong to the account, or the MDN does not belong to the specified device |
| HTTP Status 400 |
Error Code PARAMETER_ERROR |
Message Conflicting device list |
Explanation and Suggested Action The request included both allDevice=true and an exclusion list. Specify one or the other and resend the request |
| HTTP Status 400 |
Error Code PARAMETER_ERROR |
Message Max exclusion devices over limit |
Explanation and Suggested Action The number of devices specified for exclusion is more than the 2,000 device limit |
| HTTP Status 400 |
Error Code PARAMETER_ERROR |
Message Invalid device ID format |
Explanation and Suggested Action The value of the Identifier element was not in the format required by the Kind element. Set the Identifier element to a value that is in the format required by the Kind element and then resend the request |
| HTTP Status 400 |
Error Code PARAMETER_ERROR |
Message Duplicate exclusion devices |
Explanation and Suggested Action A device is included twice in the list of devices to exclude. Remove the duplicate entry and send the request again |
| HTTP Status 401 |
Error Code INVALID_ACCESS |
Message The access policy denied the resource operation for this user |
Explanation and Suggested Action The UWS account that was used to get a VZ-M2M-Token does not have access to the account specified in the request |
| HTTP Status 500 |
Error Code INTERNAL_ERROR |
Message Internal system error |
Explanation and Suggested Action Internal system error |
| HTTP Status 500 |
Error Code INTERNAL_ERROR |
Message Failed to get location |
Explanation and Suggested Action Failed to retrieve device location. Retry the request |
These errors may be returned in the error element for individual devices in a POST /locations or GET /locationreports response.
| Error Type | Info | Explanation and Suggested Action |
|---|---|---|
| Error TypeTS CACHE UNAVAILABLE | InfoLocation cache has no data | Explanation and Suggested ActionThere is no cached location information for this device. You can set cacheMode to 1 or 2 to find the current location of the device. |
| Error TypeTS CONSENT CHECK FAILED | InfoSpecified device ID was excluded from using the service | Explanation and Suggested ActionThe device is in the exclusion list, and cannot be located with the Device Location API. |
| Error TypeTS DEVICE TYPE CHECK FAILED | InfoSpecified device category is not IoT | Explanation and Suggested ActionThe specified device may be a phone or tablet. Only IoT devices can be located with the Device Location API. |
| Error TypeTS DEVICE DATA UNAVAILABLE | InfoLocation has no device data | Explanation and Suggested ActionThe device was not found in the location system |
| Error TypeTS DEVICE LOCATION DATA UNAVAILABLE | InfoLocation has no location data | Explanation and Suggested ActionThere is no location information available for the device |
| Error TypeSYSTEM FAILURE | Info | Explanation and Suggested ActionThe request can not be handled because of a general problem in the location server. |
| Error TypeUNSPECIFIED ERROR | Info | Explanation and Suggested ActionAn unspecified error used in case none of the other errors apply. This can also be used in case privacy issues prevent certain errors from being presented |
| Error TypeUNAUTHORIZED APPLICATION | Info | Explanation and Suggested ActionThe requesting location-based application is not allowed to access the location server or a wrong password has been supplied. |
| Error TypeUNKNOWN SUBSCRIBER | Info | Explanation and Suggested ActionUnknown subscriber. The user is unknown, i.e. no such subscription exists. |
| Error TypeABSENT SUBSCRIBER | Info | Explanation and Suggested ActionAbsent subscriber. The device is currently not reachable; it may be powered off or out of range. |
| Error TypePOSITION METHOD FAILURE | Info | Explanation and Suggested ActionPosition method failure. The location service failed to obtain the user’s position. |
| Error TypeTIMEOUT | Info | Explanation and Suggested ActionTimer expiry for the requested event trigger |
| Error TypeCONGESTION IN LOCATION SERVER | Info | Explanation and Suggested ActionThe request can not be handled due to congestion in the location server. |
| Error TypeUNSUPPORTED VERSION | Info | Explanation and Suggested ActionThe Location server does not support the indicated protocol version. |
| Error TypeTOO MANY POSITION ITEMS | Info | Explanation and Suggested ActionToo many position items have been specified in the request. |
| Error TypeFORMAT ERROR | Info | Explanation and Suggested ActionA protocol element in the request has invalid format. The invalid element is indicated in ADD_INFO. |
| Error TypeSYNTAX ERROR | Info | Explanation and Suggested ActionThe position request has invalid syntax. Details may be indicated in ADD_INFO. |
| Error TypePROTOCOL ELEMENT NOT SUPPORTED | Info | Explanation and Suggested ActionA protocol element specified in the position request is not supported by the Location Server, or the position result is not supported by the LCS Client. The element is indicated in ADD_INFO. |
| Error TypeSERVICE NOT SUPPORTED | Info | Explanation and Suggested ActionThe requested service is not supported in the Location Server. The service is indicated in ADD_INFO. |
| Error TypePROTOCOL ELEMENT ATTRIBUTE NOT SUPPORTED | Info | Explanation and Suggested ActionA protocol element attribute is not supported in the Location Server. The attribute is indicated in ADD_INFO. |
| Error TypeINVALID PROTOCOL ELEMENT VALUE | Info | Explanation and Suggested ActionA protocol element in the request has an invalid value. The element is indicated in ADD_INFO. |
| Error TypeINVALID PROTOCOL ELEMENT ATTRIBUTE VALUE | Info | Explanation and Suggested ActionA protocol element attribute in the request has a wrong value. The element is indicated in ADD_INFO. |
| Error TypePROTOCOL ELEMENT VALUE NOT SUPPORTED | Info | Explanation and Suggested ActionA specific value of a protocol element is not supported in the Location Server. The element and value are indicated in ADD_INFO. |
| Error TypePROTOCOL ELEMENT ATTRIBUTE VALUE NOT SUPPORTED | Info | Explanation and Suggested ActionA specific value of a protocol element attribute is not supported in the Location Server. The attribute and value are indicated in ADD_INFO. |
| Error TypeCANCELLATION OF TRIGGERED LOCATION REQUEST | Info | Explanation and Suggested ActionThe requested triggered location report is cancelled |
| Error TypeQOP NOT ATTAINABLE | Info | Explanation and Suggested ActionThe requested QoP cannot be provided. |
| Error TypePOSITIONING NOT ALLOWED | Info | Explanation and Suggested ActionThe subscriber does not allow the application to position him/her for whatever reason (privacy settings in location server, LCS privacy class). |
| Error TypeCONGESTION IN MOBILE NETWORK | Info | Explanation and Suggested ActionThe request can not be handled due to congestion in the mobile network. |
| Error TypeDISALLOWED BY LOCAL REGULATIONS | Info | Explanation and Suggested ActionThe location request is disallowed by local regulatory requirements. |
| Error TypeMISCONFIGURATION OF LOCATION SERVER | Info | Explanation and Suggested ActionThe location server is not completely configured to be able to calculate a position. |
| Error TypeTARGET MOVED TO NEW MSC/SGSN | Info | Explanation and Suggested ActionThe triggered Location Request has been aborted due to that target has moved to another MSC/SGSN. |
| Error TypeSTANDARD LOCATION REPORT SERVICE NOT SUPPORTED | Info | Explanation and Suggested ActionThe MLS Client does not support the standard location report service. |
| Error TypeMLS CLIENT ERROR | Info | Explanation and Suggested ActionAn error occurred in the MLS Client. |
| Error TypeSTANDARD LOCATION REPORT SERVICE NOT ACCEPTED | Info | Explanation and Suggested ActionThe standard location report was not accepted by the MLS Client |
| Error TypeSUBSCRIBER ID IN STANDARD LOCATION REPORT SERVICE NOT VALID | Info | Explanation and Suggested ActionThe subscriber in the Standard Location Report is not valid to the MLS Client |
| Error TypeINVALID SERVICE ID IN STANDARD LOCATION REPORT SERVICE | Info | Explanation and Suggested ActionThe service identity in the Standard Location Report is not valid to the MLS Client |
| HTTP Status | Error Code | Message | Explanation and Suggested Action |
|---|---|---|---|
| HTTP Status400 | Error CodeINVALID_PARAMETER | MessageAcct Not Provisioned With Provided Parameters. Check service & type fields | Explanation and Suggested ActionThe specified account could not be provisioned or canceled as requested. Verify that the account has been added to the primary account. |
| HTTP Status400 | Error CodeINVALID_PARAMETER | MessageInvalid Service Name | Explanation and Suggested ActionThe specified service name was not recognized. Verify the spelling and try the request again. |
| HTTP Status400 | Error CodeINVALID_PARAMETER | MessagePrimary account not registered | Explanation and Suggested ActionThe primary account specified in the request does not have any managed accounts. |
| HTTP Status400 | Error CodeINVALID_PARAMETER | MessageTxd Mismatch | Explanation and Suggested ActionThe transaction ID does not match the last action take on the account. |
| HTTP Status400 | Error CodeINVALID_PARAMETER | MessageUWS account validation failed(The contact does not have access to the account {account}.) | Explanation and Suggested ActionThe UWS user is not associated with the specified account, and cannot make any changes to that account. |