Error Codes
Last updated
Last updated
IpForensics uses conventional HTTP response codes to indicate the success or failure of an API request.
To ease debugging, quickly identify issues but also to facilitate programmatic handling, all errors include an IpForensics error code, a message that describes the problem, and a resolution field that gives guidance about how to fix the error.
BAD_REQUEST
400
You specified an invalid request payload.
ACCOUNT_TEMPORARILY_DISABLED
451
Your API key is disabled. Your account have been temporarily restricted. Contact IpForensics support service:
UNAUTHORIZED_IP
403
IP filtering is enabled for the API key in use and the user request is from an IP that you did not whitelist.
UNAUTHORIZED_ORIGIN/HOST
403
Host/Origin filtering is enabled for the API key in use and the request origin is from a host/origin that does not match the ones you allowed.
SERVER_ERROR
500
An unexpected error has occurred on IpForensics servers. Please check your request and retry again. if the issue persists.
INSUFFICIENT_TOKENS
402
Insufficient token to initiate request. You need to buy some tokens to continue using the service. Goto
INVALID_API_KEY
403
Your API key is invalid. Make sure you are using the right key or check its value for a typo.
INVALID_IP_ADDRESS
400
The IP address that was searched is not a valid IPv4 or IPv6 address.
RESERVED_IP_ADDRESS
400
The IP address that was searched is a reserved address (loopback, link-local, multicast, private, site-local or wildcard IP address). Such IP addresses cannot be used to deduce geolocation information.
LOCALHOST_IP_FORBIDDEN
403
We were unable to get your client Ipaddress. This endpoint is not to be used with localhost or local environment as they do not have valid ip address. Consider using in a live/production environment. Contact us if the issue persists.