IP Blocklist API

Overview

The IP Blocklist API provides real-time access to our continuously updated database of fraudulent IP addresses. Use it to filter invalid traffic before it impacts your campaigns, pollutes your analytics, or drains your ad budget.

Our data comes from a global sensor network monitoring over 300 million URLs and apps, encountering more than 1 billion unique users every month across exchanges, SSPs, DSPs, and publishers.

Common Use Cases

• Pre-Bid Blocking: Filter traffic before bid requests are processed in programmatic platforms
• Click Fraud Prevention: Block fraudulent clicks before they consume budget
• Affiliate Network Protection: Validate traffic and prevent fraudulent conversions
• Analytics Hygiene: Eliminate bot traffic from attribution and reporting

API Endpoint

All API requests should be made to the following endpoint:

The API accepts both GET and POST requests and returns data in JSON or CSV format.

Authentication

Every request requires authentication using your Fraudlogix credentials:

Request Parameters

Customize your API response with these optional parameters:

Example Requests

Full URL Example

https://api.fraudlogix.com/v1/prebid/blocklist?user=YOUR_USERNAME&password=YOUR_PASSWORD&version=15&risk_level=All&show_status=1&show_reason=1&method=json

cURL Example

curl -X POST https://api.fraudlogix.com/v1/prebid/blocklist \
  -d "user=YOUR_USERNAME" \
  -d "password=YOUR_PASSWORD" \
  -d "version=15" \
  -d "risk_level=All" \
  -d "show_status=1" \
  -d "show_reason=1" \
  -d "method=json"

PHP Example

$param = "user=".$username."&password=".$password.
        "&version=15".
        "&risk_level=All".
        "&show_status=1".
        "&show_reason=1".
        "&method=json";

// Initialize cURL
$ch = curl_init('https://api.fraudlogix.com/v1/prebid/blocklist');

// Set options
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST");
curl_setopt($ch, CURLOPT_POSTFIELDS, $param);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);

// Execute request
$result = curl_exec($ch);

// Process response
$data = json_decode($result, true);

Response Format

JSON Response

[
  [
    {"ip": "192.168.1.1", "status": "High", "reason_code": "Proxy"},
    {"ip": "10.0.0.1", "status": "Extreme", "reason_code": "Bot"},
    {"ip": "172.16.0.1", "status": "Medium", "reason_code": "VPN"}
  ],
  {"ref": {"status": "success", "message": ""}}
]

CSV Response

192.168.1.1,High,Proxy
10.0.0.1,Extreme,Bot
172.16.0.1,Medium,VPN

Risk Levels

Every IP in the blocklist is assigned a risk level based on the frequency and severity of fraudulent activity detected:

Reason Codes

Each IP includes a reason code explaining why it was flagged:

Integration Best Practices

• Refresh hourly: The blocklist updates every hour. Schedule syncs to match for optimal protection.
• Replace, don't merge: Always replace your local copy with the full list. IPs are removed when they show legitimate behavior.
• Handle large responses: The list contains 30M+ IPs. Ensure adequate storage and processing capacity.
• Cache locally: Store the list on your server and compare incoming IPs locally for zero-latency blocking.
• Implement fallback: If the API is temporarily unavailable, continue using your previously stored list.

Frequently Asked Questions

Need Help?

Our support team is available to assist with integration questions and technical issues.

Email: [email protected]