VPN Proxy Detector API

Overview

To use VPN Proxy Detector, you need an API key. You can get one by creating a free account and visiting your dashboard.

GET Endpoint

https://api.apiverve.com/v1/vpndetector

Example

How to call the VPN Proxy Detector API in different programming languages.

curl -X GET \
  "https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210" \
  -H "X-API-Key: your_api_key_here"

const response = await fetch('https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);

import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210', headers=headers)

data = response.json()
print(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")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

{
  "status": "ok",
  "error": null,
  "data": {
    "ip": "103.62.49.210",
    "is_vpn": false,
    "is_datacenter": true,
    "checked_on": "2025-12-16",
    "risk_level": "High",
    "threat_level": "Moderate"
  }
}

Authentication

The VPN Proxy Detector API requires authentication via API key. Include your API key in the request header:

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the VPN Proxy Detector API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the VPN Proxy Detector API:

Response

The VPN Proxy Detector API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <ip>103.62.49.210</ip>
    <is_vpn>false</is_vpn>
    <is_datacenter>true</is_datacenter>
    <checked_on>2025-12-16</checked_on>
    <risk_level>High</risk_level>
    <threat_level>Moderate</threat_level>
  </data>
</response>

status: ok
error: null
data:
  ip: 103.62.49.210
  is_vpn: false
  is_datacenter: true
  checked_on: '2025-12-16'
  risk_level: High
  threat_level: Moderate

Response Structure

All API responses follow a consistent structure with the following fields:

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access VPN Proxy Detector through GraphQL to combine it with other API calls in a single request. Query only the vpn proxy detector data you need with precise field selection, and orchestrate complex data fetching workflows.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

POST https://api.apiverve.com/v1/graphql

query {
  vpndetector(
    input: {
      ip: "103.62.49.210"
    }
  ) {
    ip
    is_vpn
    is_datacenter
    checked_on
    risk_level
    threat_level
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The VPN Proxy Detector API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

VPN Proxy Detector requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The VPN Proxy Detector API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for VPN Proxy Detector

Official VPN Proxy Detector packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

JitPack

No-Code Integrations

VPN Proxy Detector works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

People who used this also used...

Based on your interest in VPN Proxy Detector, you might also like these APIs:

USB Vendor Lookup

USB Vendor Lookup allows you to identify USB device manufacturers and products by their vendor ID and product ID. It uses the Linux USB ID Repository, which contains thousands of USB vendor and product identifiers.

1 credit per call

Tor Node Detector

Tor Detect is an API that checks whether a given IP address belongs to a known Tor exit node. Useful for security, access control, and analytics.

1 credit per call

TLS Checker

TLS Check is an API that inspects the TLS/SSL configuration of a server identified by its IP address. It reports supported protocols, cipher suites, and potential vulnerabilities.

1 credit per call