VPN Proxy Detector API

GET Endpoint

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

Code Examples

Here are examples of 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)

const https = require('https');
const url = require('url');

const options = {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const req = https.request('https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.end();

<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($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))
}

require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))

using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;

class Program
{
    static async Task Main(string[] args)
    {
        using var client = new HttpClient();
        client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");

        var response = await client.GetAsync("https://api.apiverve.com/v1/vpndetector?ip=103.62.49.210");
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

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:

Example Responses

{
  "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"
  }
}

<?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

Required and optional headers for VPN Proxy Detector API requests:

Learn more about 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 supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call VPN Proxy Detector directly from browser-based applications without proxy servers.

Browser Usage: You can call VPN Proxy Detector directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

VPN Proxy Detector API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all VPN Proxy Detector users.

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each VPN Proxy Detector response includes headers to help you track your usage:

Handling Rate Limits

Free Plan: When you exceed your rate limit, VPN Proxy Detector returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.

Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.

Best Practices for VPN Proxy Detector:

• Monitor the rate limit headers to track your VPN Proxy Detector usage (Free plan only)
• Cache vpn proxy detector responses where appropriate to reduce API calls
• Upgrade to Pro or Mega for guaranteed no-throttle VPN Proxy Detector performance

Note: VPN Proxy Detector rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using VPN Proxy Detector on Free tier.

Error Codes

The VPN Proxy Detector API uses standard HTTP status codes to indicate success or failure:

Learn more about error handling →

Need help? Contact support with your X-Request-ID for assistance.

Integrate VPN Proxy Detector with SDKs

Get started quickly with official VPN Proxy Detector SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.

Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.

JitPack

Integrate VPN Proxy Detector with No-Code API Tools

Connect the VPN Proxy Detector API to your favorite automation platform without writing code. Build workflows that leverage vpn proxy detector data across thousands of apps.

ZapierConnect VPN Proxy Detector to 6,000+ apps

MakeBuild visual vpn proxy detector workflows

PipedreamCode-friendly vpn proxy detector automation

n8nSelf-host your vpn proxy detector workflows

Power AutomateUse VPN Proxy Detector in Microsoft 365

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