Errors and Error Codes

Contents

• Errors and Error Codes
  • Common Errors
  • Error Codes
    • Request Errors
    • Per-Device Errors
    • Managed Account Errors

Common Errors

Trying to log in with an expired ThingSpace token:

{
    "fault": {
        "code": "900901",
        "message": "Invalid Credentials",
        "description": "Access failure for API: /m2m/v1, version: v1. Make sure your have given the correct access token"
    }
}

Expired VZ-M2M token

{
    "error": "unauthorized",
    "error_description": "Failure response received for UWS V1 REST accounts: [400]",
    "cause": "Requested service is unauthorized for given token"
}

Bad format for ThingSpace token:

{
    "error": "internal_server_error",
    "error_description": "configuration on Device field failed with Error: unauthorized: Failure response received for UWS V1 REST accounts: [401], Requested service is unauthorized for given token",
    "cause": "Requested service failed due to internal error"
}

Attempting to add a device without providing the billingaccountid:

{
    "error": "bad_request",
    "error_description": "Billing Account ID is required in resource body",
    "cause": "Request is missing required body content"
}

Bad JSON, or data type mismatch. Using a string for an IMEI instead of a number:

{
    "error": "request_json_unmarshal",
    "error_description": "JSON structure is not correct or data type mismatch, json: cannot unmarshal string into Go struct field V1DeviceIdentifier.imei of type uint64",
    "cause": "Service failed to unmarshal the request due wrong JSON format"
}

Trying to delete a device using a bogus IMEI:

{
    "error": "not_found",
    "error_description": "Resource(Device) is not found with identifiers provided",
    "cause": "Requested service not found"
}

Trying to activate a device when it had been deleted:

{
    "error": "bad_request",
    "error_description": "Resource(Device) is not found with identifiers provided",
    "cause": "Request is missing required body content"
}

Setting "kind" to ts.target in PUT /tags:

{
    "error": "bad_request",
    "error_description": "ValidationKind failed. Types do not match, Target vs Tag",
    "cause": "Request is missing required body content"
}

Trying to activate a "ready" CAS device:

{
    "error": "invalid_event",
    "error_description": "Operation cannot be completed. Invalid event[activate] for device state:ready"
}

Setting Frequency value to"high" instead of "High"

{
    "error": "internal_server_error",
    "error_description": "configuration on Device field failed with Error: provider_service_error: provider: ORIGINAL_ERROR_FROM_PROVIDER, Bad Request: null\n, , Failed to forward event to channel due to error",
    "cause": "Requested service failed due to internal error"
}

Setting the Frequency value to High when it was already set to that value, and not setting the Location Mode.

{
    "error": "internal_server_error",
    "error_description": "configuration on Device field failed with Error: provider_service_error: provider: ORIGINAL_ERROR_FROM_PROVIDER, bad_request: Neither Location Mode Nor Frequency Changed in the request, , Failed to forward event to channel due to error",
    "cause": "Requested service failed due to internal error"
}
`

Error Codes

Request Errors

All ThingSpace Location Services API resources use this set of status codes in responses.

Per-Device Errors

These errors may be returned in the error element for individual devices in a POST /locations or a GET /locationreports response.

Managed Account Errors