pricing background

API Errors & Status Codes

Understand API error responses, status codes, and error formatting to debug issues and handle failures effectively.

Error Formatting

Below is a sample structure of how API error responses are formatted. This helps you understand the fields returned when a request fails, so you can debug issues and handle errors effectively in your integration.

JSON 
{
  "timestamp": "2024-07-10T13:38:43.883Z",
  "status": 400,
  "error": "Invalid Param Exception",
  "message": "Please pass domain param correct value[For Technical Support: [email protected]]",
  "path": "/v1.0/domain/availability"
}
  • Error: Indicates the type or category of the error that occurred.
  • Message: Provides a detailed explanation of the issue to help identify what went wrong.
  • Path: Shows the API endpoint where the error was triggered.

Status Codes

The following status codes indicate the outcome of your API requests. Success codes confirm that the request was processed correctly, while failure codes highlight issues that need attention, helping you handle responses and debug errors more effectively.

Success Codes
  • 200  Request is processed successfully.
  • 206  Partial response, as an error occurred while processing the request.
  • 210  Cached response, as the WHOIS server failed to respond.
Failure Codes
  • 400  Please pass domain param correct value e.g. whoisfreaks.com, https://whoisfreaks.com, http://whoisfreaks.com
  • 400  Please provide data in request body.
  • 400  Please provide one of the keyword or pattern, both are not acceptable
  • 400  Please provide domainNames in request body.
  • 400  Please provide keyword or pattern.
  • 400  Please pass apiKey param value.
  • 400  Please provide the date parameter.
  • 400  Invalid date parameter.
  • 400  Provided date is too old.
  • 400  Please provide IPs in the request body.
  • 400  Provided name, service or IP address 'XXX.XXX.XXX.XXX' is not valid.
  • 400  The domain name field is required and cannot be left empty or null. Please provide a valid domain name to proceed.
  • 400  'after' date must be earlier than 'before' date.
  • 400  'after' date cannot be greater than the current date.
  • 400  fileType is not found.
  • 400  Request-param 'ip' (<ip>) is not valid.
  • 400  Request-param 'format' (<format>) is not valid. Supported formats are json, xml.
  • 400  Request-param 'asn' (******) is not valid.
  • 400  Unable to process request.
  • 400  Please provide correct value Param
  • 401  Provided API key is invalid.
  • 401  Provided API key is inactive.
  • 401  Please buy a subscription plan or add api credits, then use this api key.
  • 401  Your subscription is deactivated. Please buy new plan or add api credits for using whoisfreaks APIs.
  • 401  Your subscription is deactivated due to much time payment failure. Please buy a new plan or add api credits for using whoisfreaks APIs.
  • 401  Your account is deactivated.
  • 401  You are blocked due to suspicious activity.
  • 401  Api record not found.
  • 401  Please buy domainer package.
  • 401  Your domainer package plan is inactive.
  • 401  You cannot download file.
  • 401  You have exceeded the download limit of 20000.
  • 401  Suspicious Activity.
  • 401  Please buy database subscription.
  • 401  Your database subscription plan is inactive.
  • 403  We are not providing the whois of this domain extension (e.g., comsdf)
  • 403  Provided domain belongs to an inactive TLD. Please try to use historical whois lookup.
  • 404  The requested IP does not not exists in our database.
  • 404  Record not found.
  • 404  File is not available of this date.
  • 404  Resources are not available of this date.
  • 404  The requested IP does not not exists in our database.
  • 404  No Ssl Certificate exists for this Domain.
  • 404  No Record Found across domainName.
  • 404  Entered Domain does not exist.
  • 405  Invalid HTTP request method is being used for calling the endpoint. Only GET and POST methods are allowed. POST method for bulk endpoint and GET method for single lookup endpoint requests.
  • 408  Unable to fetch whois data. Please try again.
  • 408  Unable to process request.
  • 408  Unable to fetch dns records. Please try after some time.
  • 412  You have exceeded the limit of api plan requests and your subscription is canceled.
  • 413  You have exceeded the limit of api credits requests [allowed_request_no]. Please upgrade your plan.
  • 413  You have exceeded the limit of Surcharge Requests [allowed_surcharge_request_no]. Please upgrade your plan.
  • 413  The requested list size is [GREATER_THAN_100] which exceeds the maximum list size of 100.
  • 413  Please upgrade your plans.
  • 423  The IP address you provided falls within bogon IP ranges, which are not routable on the public internet. Please make sure to use a valid, publicly accessible IP address for accurate results.
  • 429  Please slow down. Your maximum request limit per minute is reached.
  • 499  The request or connection timeout you’ve set is too short, which is causing the server to close the connection before completing the response. Please increase the timeout duration to ensure successful communication with the server.
  • 500  Internal Server error occurred.
  • 502  Please provide ips in request body.
  • 503  Service is unavailable. Please try after some time.
  • 504  Request is timed-out.
  • 505  You might be using an outdated HTTP version.