Bot Detector API

GET Endpoint

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

Code Examples

Here are examples of how to call the Bot Detector API in different programming languages:

curl -X GET \
  "https://api.apiverve.com/v1/botdetector" \
  -H "X-API-Key: your_api_key_here"

const response = await fetch('https://api.apiverve.com/v1/botdetector', {
  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/botdetector', 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/botdetector', 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/botdetector');
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/botdetector", 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/botdetector')
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/botdetector");
        response.EnsureSuccessStatusCode();

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

Authentication

The Bot 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 Bot Detector API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Bot Detector API:

Response

The Bot Detector API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

{
  "status": "ok",
  "error": null,
  "data": {
    "userAgent": "Googlebot/2.1 (+http://www.google.com/bot.html)",
    "isBot": true,
    "bot": {
      "name": "Googlebot",
      "category": "search_engine",
      "url": "http://www.google.com/bot.html"
    }
  }
}

<?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>
    <userAgent>Googlebot/2.1 (+http://www.google.com/bot.html)</userAgent>
    <isBot>true</isBot>
    <bot>
      <name>Googlebot</name>
      <category>search_engine</category>
      <url>http://www.google.com/bot.html</url>
    </bot>
  </data>
</response>

status: ok
error: null
data:
  userAgent: Googlebot/2.1 (+http://www.google.com/bot.html)
  isBot: true
  bot:
    name: Googlebot
    category: search_engine
    url: http://www.google.com/bot.html

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 Bot Detector API requests:

Learn more about request headers →

GraphQL AccessALPHA

Access Bot Detector through GraphQL to combine it with other API calls in a single request. Query only the bot 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 {
  botdetector(
    input: {
      ua: "Googlebot/2.1 (+http://www.google.com/bot.html)"
    }
  ) {
    userAgent
    isBot
    bot {
      name
      category
      url
    }
  }
}

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

CORS Support

The Bot Detector API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Bot Detector directly from browser-based applications without proxy servers.

Browser Usage: You can call Bot 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

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

Learn more about rate limiting →

Rate Limit Headers

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

Handling Rate Limits

Free Plan: When you exceed your rate limit, Bot 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 Bot Detector:

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

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

Error Codes

The Bot 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 Bot Detector with SDKs

Get started quickly with official Bot 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 Bot Detector with No-Code API Tools

Connect the Bot Detector API to your favorite automation platform without writing code. Build workflows that leverage bot detector data across thousands of apps.

ZapierConnect Bot Detector to 6,000+ apps

MakeBuild visual bot detector workflows

PipedreamCode-friendly bot detector automation

n8nSelf-host your bot detector workflows

Power AutomateUse Bot Detector in Microsoft 365

Frequently Asked Questions

People who used this also used...

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

VPN Proxy Detector

VPN Detector is a simple tool for detecting VPN usage. It returns a boolean value indicating whether the IP address is using a VPN or not.

1 credit per call

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