Migrate from v1 to v2

If you are still using the APIVoid v1 endpoints, this guide covers everything needed to migrate to the v2 API. The v2 API introduces improved authentication, a cleaner JSON structure, and a more standardized request format. The complete v2 reference starts at the documentation home.

1. HTTP method and authentication

In v1, requests used HTTP GET, with the API key passed in the query string via key=:

curl "https://endpoint.apivoid.com/iprep/v1/pay-as-you-go/?key=YOUR_API_KEY_HERE&ip=122.226.181.165"

In v2, requests use HTTP POST, the API key is sent in the X-API-Key header, and parameters go in a JSON body:

curl -X POST "https://api.apivoid.com/v2/ip-reputation" \
     -H "Content-Type: application/json" \
     -H "X-API-Key: YOUR_API_KEY_HERE" \
     -d '{"ip": "122.226.181.165"}'

What changed:

• HTTP method: GET → POST
• API key moved from the query string to the X-API-Key header. See Authentication.
• Parameters moved from the URL to the JSON request body.
• New base URL: https://api.apivoid.com/v2/
• New URL path per API, e.g. ip-reputation for IP Reputation API (see the API reference pages).

2. JSON response structure

Important breaking change: the root data object and the data.report wrapper were removed.

The v1 response structure:

{
  "data": {
    "report": {
      "ip": "80.82.77.139",
      "blacklists": {
        ...
      }
    }
  }
}

To access the IP field in v1: response.data.report.ip

The v2 response structure:

{
  "ip": "80.82.77.139",
  "version": "IPv4",
  "blacklists": {
    ...
  }
}

To access the IP field in v2: response.ip

What changed:

• Removed the data root object.
• Removed the report wrapper.
• Fields are now at the top level of the JSON response.
• Cleaner and flatter structure; the exact fields for each API are documented on its reference page.

3. Migration checklist

• If not already done, create a v2 account.
• Use the API keys from the new v2 dashboard.
• Check the v2 API documentation for each API you use.
• Change the HTTP method from GET to POST.
• Move the API key from the query parameter to the X-API-Key header.
• Send request parameters as a JSON body with Content-Type: application/json.
• Update the base URL to https://api.apivoid.com/v2/.
• Update the URL path for each API (e.g. ip-reputation).
• Update your response parsing logic (remove data.report).
• Review API errors & retries and rate limits, which also changed in v2.