Bot DetectorBot Detector API

OnlineCredit Usage:1 per callRefreshed 5 days ago
avg: 120ms|p50: 116ms|p75: 123ms|p90: 132ms|p99: 149ms

Overview

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

GET Endpoint

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

Example

How to call the Bot Detector API in different programming languages.

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/botdetector?ua=Googlebot%2F2.1%20(%2Bhttp%3A%2F%2Fwww.google.com%2Fbot.html)" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/botdetector?ua=Googlebot%2F2.1%20(%2Bhttp%3A%2F%2Fwww.google.com%2Fbot.html)', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

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

response = requests.get('https://api.apiverve.com/v1/botdetector?ua=Googlebot%2F2.1%20(%2Bhttp%3A%2F%2Fwww.google.com%2Fbot.html)', headers=headers)

data = response.json()
print(data)
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"

)

func main() {
    req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/botdetector?ua=Googlebot%2F2.1%20(%2Bhttp%3A%2F%2Fwww.google.com%2Fbot.html)", 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))
}
Example 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",
      "reputation": "trusted",
      "shouldBlock": false
    }
  }
}

Authentication

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

Required 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:

Check if User Agent is a Bot

ParameterTypeRequiredDescriptionDefaultExample
uastringrequired
The user agent string to analyze (URL encoded)
-Googlebot/2.1 (+http://www.google.com/bot.html)

Response

The Bot 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 Response
200 OK
<?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>
      <reputation>trusted</reputation>
      <shouldBlock>false</shouldBlock>
    </bot>
  </data>
</response>
YAML Response
200 OK
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
    reputation: trusted
    shouldBlock: false
CSV Response
200 OK
keyvalue
userAgentGooglebot/2.1 (+http://www.google.com/bot.html)
isBottrue
bot{name:Googlebot,category:search_engine,url:http://www.google.com/bot.html,reputation:trusted,shouldBlock:false}

Response Structure

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

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains 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:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
userAgentstring"Googlebot/2.1 (+http://www.google.com/bot.html)"
The analyzed user agent string provided in the request
isBotbooleantrue
Whether the user agent belongs to a known bot or crawler
botPremiumobject{...}
Detailed bot information including name, category, and reputation
â”” namestring"Googlebot"
Name of the detected bot or crawler
â”” categorystring"search_engine"
Category of bot: search_engine, social_media, monitoring, seo_tool, scraper, other
â”” urlstring"http://www.google.com/bot.html"
Official URL or documentation link for the bot
â”” reputationstring"trusted"
Trust level: trusted (search engines, social), neutral (monitoring, SEO), malicious (scrapers, spam), or unknown
â”” shouldBlockbooleanfalse
Recommendation whether to block this bot based on category and reputation

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

Test Bot Detector in the GraphQL Explorer to confirm availability and experiment with queries.

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

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  botdetector(
    input: {
      ua: "Googlebot/2.1 (+http://www.google.com/bot.html)"
    }
  ) {
    userAgent
    isBot
    bot {
      name
      category
      url
      reputation
      shouldBlock
    }
  }
}

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

Bot 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 Bot 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 Bot Detector

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

No-Code Integrations

Bot 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 Bot Detector?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Bot Detector and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Bot Detector cost?

Each successful Bot 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 bot detector lookups.

Can I use Bot Detector in production?

The free plan is for testing and development only. For production use of Bot 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 Bot Detector from a browser?
Yes! The Bot Detector API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Bot Detector credit limit?

When you reach your monthly credit limit, Bot 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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?