Overview
Send an IPv4 or IPv6 address to inspect its routing and hosting profile against daily updated network lists. The API flags whether the address routes through a commercial VPN or a cloud datacenter. Paid plans also return Tor exit node status, Autonomous System Numbers (ASN), and assigned risk and threat levels.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
ipRequired | string | The IP address you want to check for VPN usage ip |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"ip": "103.62.49.210",
"is_vpn": false,
"is_datacenter": true,
"is_tor": false,
"asn": "AS137409",
"asn_name": "GSLNETWORKS-AS-AP GSL Networks Pty LTD",
"checked_on": "2026-09-14",
"risk_level": "Moderate",
"threat_level": "Low"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
ip | string | "103.62.49.210" | The IP address that was checked for VPN usage |
is_vpn | boolean | false | Whether the IP address is using a VPN service |
is_datacenter | boolean | true | Whether the IP belongs to a datacenter or cloud provider |
is_torPremium | boolean | false | Whether the IP is a known Tor exit node; null if the Tor list could not be checked |
asnPremium | string | "AS137409" | Autonomous System Number announcing the IP (e.g., AS16509); null if unrouted |
asn_namePremium | string | "GSLNETWORKS-AS-AP GSL Networks Pty LTD" | Registered name of that AS (e.g., AMAZON-02), not always the company name |
checked_on | string | "2026-09-14" | The date when the IP was last checked for VPN status |
risk_levelPremium | string | "Moderate" | Overall risk of the IP address: High for Tor exits and VPNs, Moderate for datacenter-only addresses, Low otherwise |
threat_levelPremium | string | "Low" | How strongly the IP anonymises its user: High for Tor exits, Moderate for VPNs, Low otherwise |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Fraudulent Signup Prevention
- To stop fake account spam, security platforms verify visitor IPs at registration to block traffic originating from known commercial VPNs and cloud servers.
- Streaming Rights Compliance
- Media providers check playback requests against datacenter and VPN flags to enforce territorial broadcasting rights on copyrighted video catalogs.
- Payment Gateway Screening
- When an online order is submitted, checkout systems check the buyer IP to trigger extra authentication steps if it belongs to a datacenter network.
- Ad Click Validation
- Advertising networks filter invalid traffic by screening incoming ad impressions for datacenter hosting IPs before recording billable user interactions.
Other ways to use VPN Proxy Detector
Set up VPN Proxy Detector on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
Pages that use this API:
- Block fake signupsGuides
More in Networking: