LI Error Codes

Learn how to use error codes to identify and remedy content, authentication, and server errors in Location Intelligence API requests.

Location Intelligence error codes are returned when the platform is unable to process a request.

The error code accompanies and clarifies a standard 4xx status code. If the error can be handled programmatcially, the error code provides a brief explanation of the error or suggests a solution.

ERR_4000
Bad request.
ERR_4001
Insufficient geocoding information. A required field is missing.
ERR_4002
Insufficient geocoding resolution to look up requested data.
ERR_4003
Location is in a region that is not supported by this hazard layer.
ERR_4005
Insufficient information to look up requested data.
ERR_4010
Forbidden.
ERR_4030
Unauthorized.
ERR_4040
Not found.
ERR_4041
Invalid input.
ERR_4050
Method not allowed.
ERR_4060
Not acceptable.
ERR_4080
Request timeout.
ERR_4100
Not a valid distanceUnit option. Valid distanceUnit options are meters and feet.
ERR_4102
Not valid returnPeriod option. Valid returnPeriod options are 30, 50, 100, 200, 250, 500, and 1000.
ERR_4103
Not a valid defended option. Valid defended options are true and false.
ERR_4104
Not a valid proximityDistance option. Valid proximityDistance is a positive number.
ERR_4105
Not a valid distanceUnit option. Valid distanceUnit options are feet, meters, miles, and km.
ERR_4106
Insufficient information to look up requested data. Missing one or both of distanceUnit and proximityDistance.
ERR_4130
Request too large.
ERR_4150
Unsupported media type.
ERR_4220
Unprocessable entity.
ERR_4290
Quota exceeded.
ERR_4300
Not a valid basement. Valid basements are yes, no, and default.
ERR_4400
Geocoding error.
ERR_4401
Invalid address input. Field is incorrect.
ERR_5000
Internal server error.
ERR_5040
Gateway timeout.