We're thrilled to announce that WHOIS queries can now be processed through POST requests in addition to the current HTTP GET request method. This new capability offers a more secure way to access domain registration information.

Using POST requests significantly reduces the risk of unauthorized access to API keys, as they encrypt the HTTP message body, including the API key. To illustrate, here is an example of a POST request.

curl --location 'https://www.whoisxmlapi.com/whoisserver/WhoisService' \
--header 'Content-Type: application/json' \
--data '{
    "apiKey": "at_*************************",
    "domainName": "whoisxmlapi.com",
    "outputFormat": "json"
}'

* The data (or the body) is encrypted using HTTPS.

With this new method, WhoisXML API users can:

• Enhance security: Since the API key and other sensitive details are embedded within the encrypted request body, using POST helps protect user credentials.

• Improve user confidence: Users seeking to integrate WHOIS API into their systems can rest assured that their API key data is protected.

• Continue using a reliable service: Transitioning to using POST will not affect the API’s functionality, performance, or credit usage.

How Difficult Is Transitioning to POST?

WHOIS API users can already start switching to POST. While the HTTP GET request method will remain available, a common question users ask pertains to the difficulty in shifting from WHOIS queries using GET to POST requests.

The difficulty level depends on several factors, such as the OS, developer environment, scripts, and programming language users utilize. Customers' automation tools can also affect the transition process since some tools can (or cannot) readily adapt to POST request usage.

—

As WhoisXML API continues to improve products based on customer feedback, expect more features and capabilities that will enhance security and user experiences.

To learn more about this new method for making WHOIS API requests, visit this page or contact us.