IP Security and User Agent Analyzer API

API ID 14754

Inspect visitor IP addresses and User-Agent strings in a single call to identify automated bots, VPNs, proxies, suspicious traffic, OS, browser, and device types.

API Documentation

Endpoints

Request
Analyzes a visitor's IPv4/IPv6 address and HTTP User-Agent string in real time to detect automated bots, crawlers, VPNs, proxies, Tor nodes, and extract detailed client device, OS, and browser metadata.
Endpoint ID: 38182
GET https://zylalabs.com/api/14754/ip+security+and+user+agent+analyzer+api/38182/inspect+ip+and+user+agent
INPUT PARAMETERS

Inspect IP and User Agent — Endpoint Features

Object Description
ip Required The visitor IPv4 or IPv6 address to analyze.
ua Required The raw HTTP User-Agent string of the client.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

ip
ua
API EXAMPLE RESPONSE
JSON
{
    "status": "success",
    "message": "Access check completed.",
    "data": {
        "ip": {
            "query": "149.86.140.210",
            "type": "IPv4",
            "is_private": false,
            "country": "Türkiye",
            "isp": "Gibirnet Iletisim Hizmetleri Sanayi VE Ticaret Limited Sirketi",
            "org": "Gibirnet Iletisim Hizmetleri Sanayi VE Ticaret Limited Sirketi",
            "is_blacklisted": true,
            "suggest": "block",
            "reason": "proxy"
        },
        "ua": {
            "is_bot": false,
            "raw": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:158.0) Gecko/20100101 Firefox/158.0"
        }
    },
    "response": "5ms",
    "website": "https://botsec.dev",
    "contact": "https://t.me/AozoraKZ"
}
Inspect IP and User Agent — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14754/ip+security+and+user+agent+analyzer+api/38182/inspect+ip+and+user+agent?ip=149.86.140.210&ua=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:158.0) Gecko/20100101 Firefox/158.0' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Inspects an IP address to determine if it originates from a known VPN, proxy, Tor node, datacenter, or malicious bot source.
Endpoint ID: 38183
GET https://zylalabs.com/api/14754/ip+security+and+user+agent+analyzer+api/38183/check+ip+block+and+vpn+status
INPUT PARAMETERS

Check IP Block and VPN Status — Endpoint Features

Object Description
ip Required Target IP address to check for security status

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

ip
API EXAMPLE RESPONSE
JSON
{
    "status": "success",
    "message": "IP reputation checked.",
    "data": {
        "query": "134.209.29.120",
        "type": "IPv4",
        "is_private": false,
        "country": "United Kingdom",
        "isp": "DigitalOcean, LLC",
        "org": "DigitalOcean, LLC",
        "is_blacklisted": true,
        "suggest": "block",
        "reason": "proxy"
    },
    "response": "0ms",
    "website": "https://botsec.dev",
    "contact": "https://t.me/AozoraKZ"
}
Check IP Block and VPN Status — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14754/ip+security+and+user+agent+analyzer+api/38183/check+ip+block+and+vpn+status?ip=134.209.29.120' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Parses raw HTTP User-Agent strings to extract detailed client device categories, operating systems, browser versions, and hardware footprints.
Endpoint ID: 38184
GET https://zylalabs.com/api/14754/ip+security+and+user+agent+analyzer+api/38184/parse+user-agent+device+metadata
INPUT PARAMETERS

Parse User-Agent Device Metadata — Endpoint Features

Object Description
ua Required Raw HTTP user-agent string to parse

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

ua
API EXAMPLE RESPONSE
JSON
{
    "status": "success",
    "message": "Device information retrieved successfully.",
    "data": {
        "is_bot": false,
        "device": {
            "name": "desktop",
            "brand": "",
            "model": ""
        },
        "client": {
            "type": "browser",
            "name": "Firefox",
            "short_name": "FF",
            "version": "159.0",
            "engine": "Gecko",
            "engine_version": "159.0",
            "family": "Firefox"
        },
        "os": {
            "name": "Windows",
            "short_name": "WIN",
            "version": "10",
            "platform": "x64",
            "family": "Windows"
        },
        "raw": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:159.0) Gecko/20100101 Firefox/159.0"
    },
    "response": "94ms",
    "website": "https://botsec.dev",
    "contact": "https://t.me/AozoraKZ"
}
Parse User-Agent Device Metadata — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14754/ip+security+and+user+agent+analyzer+api/38184/parse+user-agent+device+metadata?ua=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:159.0) Gecko/20100101 Firefox/159.0' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the IP Security and User Agent Analyzer API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

(Save 2 months with annual billing 🎉)

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Inspect visitor IP addresses and User-Agent strings in a single call to identify automated bots, VPNs, proxies, suspicious traffic, OS, browser, and device types.

IP Security and User Agent Analyzer API FAQs

The endpoint returns data about the visitor's IP address and User-Agent string, including details like the IP type (IPv4/IPv6), geographical location, ISP, organization, and whether the IP is blacklisted. It also provides information on whether the User-Agent is a bot and includes the raw User-Agent string.

Key fields in the response include "ip" (with subfields like "query," "type," "country," "isp," "is_blacklisted," and "suggest") and "ua" (with "is_bot" and "raw"). These fields provide comprehensive insights into the visitor's identity and behavior.

The response data is structured in a JSON format with a top-level object containing "status," "message," "data," "response," "website," and "contact." The "data" field further contains nested objects for "ip" and "ua," allowing for easy access to specific information.

The endpoint provides information on the visitor's IP address (location, ISP, organization, blacklist status) and User-Agent (bot detection, device type, OS, and browser). This data helps identify suspicious traffic and understand user demographics.

The data is sourced from various databases and services that track IP addresses, ISPs, and User-Agent strings. This includes public and proprietary datasets to ensure comprehensive coverage and accuracy in identifying bots, proxies, and other traffic types.

Typical use cases include fraud detection, bot management, traffic analysis, and enhancing security measures. Businesses can use this data to block malicious traffic, tailor user experiences, and monitor for suspicious activity on their websites.

Users can customize requests by specifying the IP address and User-Agent string they wish to analyze. This allows for targeted inspections of specific visitors, enabling detailed insights into their behavior and potential risks.

Users can utilize the returned data to make informed decisions about traffic management, security protocols, and user engagement strategies. For example, if an IP is flagged as suspicious, users can choose to block it or investigate further.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs