Tor Node Detector API
Overview
To use Tor Node 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/tordetectExample
How to call the Tor Node Detector API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/tordetect?ip=185.189.183.143" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/tordetect?ip=185.189.183.143', {
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/tordetect?ip=185.189.183.143', 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/tordetect?ip=185.189.183.143", 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": {
"ipAddress": "185.189.183.143",
"isTor": true,
"ipDetails": {
"range": [
3116217344,
3116218367
],
"country": "NL",
"region": "ZH",
"timezone": "Europe/Amsterdam"
},
"parsed": true
}
}Authentication
The Tor Node Detector API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Tor Node Detector API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Tor Node Detector API:
Check IP Against Tor Exit Node List
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
ip | string | required | The IP address to check against the Tor exit node list Format: ip (e.g., 185.189.183.143) | - |
Response
The Tor Node 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>
<ipAddress>185.189.183.143</ipAddress>
<isTor>true</isTor>
<ipDetails>
<range>
<item>3116217344</item>
<item>3116218367</item>
</range>
<country>NL</country>
<region>ZH</region>
<timezone>Europe/Amsterdam</timezone>
</ipDetails>
<parsed>true</parsed>
</data>
</response>
status: ok
error: null
data:
ipAddress: 185.189.183.143
isTor: true
ipDetails:
range:
- 3116217344
- 3116218367
country: NL
region: ZH
timezone: Europe/Amsterdam
parsed: true
| key | value |
|---|---|
| ipAddress | 185.189.183.143 |
| isTor | true |
| ipDetails | {range:[3116217344,3116218367],country:NL,region:ZH,timezone:Europe/Amsterdam} |
| parsed | true |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
ipAddress | string | The IP address being checked for Tor exit node status | |
isTor | boolean | Whether the IP is a known Tor exit node | |
ipDetailsPremium | object | Detailed information about the IP geolocation and network | |
â”” rangePremium | array | IP address range in numeric format for this location | |
â”” country | string | Two-letter ISO country code of IP location | |
â”” region | string | Region or state code of IP location within country | |
â”” timezone | string | IANA timezone identifier for IP location | |
parsed | boolean | Whether the IP address was successfully parsed and validated |
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 Tor Node Detector through GraphQL to combine it with other API calls in a single request. Query only the tor node 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/graphqlquery {
tordetect(
input: {
ip: "185.189.183.143"
}
) {
ipAddress
isTor
ipDetails {
range
country
region
timezone
}
parsed
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Tor Node 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
Tor Node 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 Tor Node 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 Tor Node Detector
Official Tor Node Detector packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Tor Node Detector works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Tor Node Detector?
How many credits does Tor Node Detector cost?
Each successful Tor Node Detector API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful tor node detector lookups.
Can I use Tor Node Detector in production?
The free plan is for testing and development only. For production use of Tor Node Detector, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Tor Node Detector from a browser?
What happens if I exceed my Tor Node Detector credit limit?
When you reach your monthly credit limit, Tor Node Detector API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








