SDKs overview

Software Development Kits (SDKs) and libraries for the IPQualityScore API facilitate the integration of its fraud detection and prevention services into various applications. These tools abstract the underlying HTTP requests and response parsing, allowing developers to focus on application logic rather than the intricacies of API communication. IPQualityScore provides official documentation with code examples across several popular programming languages, detailing how to interact with its core products, including fraud scoring, email validation, and VPN/proxy detection. The availability of these examples helps accelerate development cycles by offering ready-to-use functions for common API operations. Developers can find comprehensive guides within the IPQualityScore documentation portal that illustrate how to configure and utilize the API for specific use cases like detecting suspicious user registrations or transactional fraud.

While IPQualityScore does not currently list formally packaged SDKs on public repositories like Maven Central or npm, their documentation provides direct code examples and integration instructions for common programming environments. This approach allows for flexibility, enabling developers to integrate the API using standard HTTP client libraries available in their chosen language. The examples cover essential API interactions, from sending a request to the IP Reputation API to parsing the JSON response for fraud scores and risk factors. This method of providing integration guidance is common among RESTful APIs, where the fundamental communication relies on HTTP methods and JSON payloads, as detailed by the IETF HTTP Semantics specification.

Official SDKs by language

IPQualityScore provides official code examples and integration instructions for several programming languages directly within their documentation. These examples serve as de facto SDKs, offering pre-written functions and structures to interact with the API endpoints efficiently. The approach emphasizes direct integration using standard HTTP client libraries, which ensures compatibility across various environments without requiring specific package installations beyond the language's core capabilities. This section outlines the primary languages for which IPQualityScore offers detailed integration guidance, including setup instructions and example API calls.

Language Integration Method Key Features Documentation Link
PHP cURL or Guzzle HTTP client IP reputation checks, email validation, transaction scoring PHP Proxy/VPN Detection API example
Python Requests library Fraud scoring, phone number validation, bot detection Python Proxy/VPN Detection API example
Ruby Net::HTTP or HTTParty gem IP address analysis, email validation, user risk assessment Ruby Proxy/VPN Detection API example
Node.js Axios or native HTTPS module Real-time fraud detection, transaction risk analysis Node.js Proxy/VPN Detection API example
Java HttpClient (Apache) or OkHttp Fraud prevention, email and phone verification Java Proxy/VPN Detection API example
C# HttpClient (.NET) Bot detection, IP reputation, email scoring C# Proxy/VPN Detection API example

Installation

Since IPQualityScore primarily provides direct code examples rather than installable packages for all languages, installation typically involves setting up a basic HTTP client in your chosen programming environment. The process generally includes:

  1. Obtaining an API Key: Register for an IPQualityScore account and retrieve your unique API key from the dashboard. This key is essential for authenticating your API requests.
  2. Setting up an HTTP Client:
    • PHP: Use curl directly or install a library like Guzzle via Composer (composer require guzzlehttp/guzzle).
    • Python: Install the Requests library (pip install requests).
    • Ruby: The standard library Net::HTTP can be used, or install httparty (gem install httparty).
    • Node.js: Install Axios (npm install axios) or use the built-in https module.
    • Java: Add Apache HttpClient or OkHttp to your project dependencies (e.g., via Maven or Gradle).
    • C#: Utilize the built-in HttpClient class available in .NET.
  3. Copying Example Code: Integrate the relevant code snippets from the IPQualityScore API reference into your application.
  4. Configuring Endpoints and Parameters: Customize the API endpoint URL, API key, and request parameters based on the specific IPQualityScore service you intend to use (e.g., IP reputation, email validation).

For instance, to install the Requests library in Python, you would open your terminal or command prompt and execute pip install requests. This command downloads and installs the necessary package, making it available for import in your Python scripts. Similar package managers like npm for Node.js (npm install axios) or Composer for PHP (composer require guzzlehttp/guzzle) streamline the process of adding external libraries. Java and C# projects typically manage dependencies through build tools like Maven, Gradle, or NuGet, where you declare the required libraries in a configuration file, and the build system handles the download and linking.

Quickstart example

This Python example demonstrates how to perform an IP address reputation check using the IPQualityScore API and the requests library. Replace YOUR_API_KEY with your actual IPQualityScore API key.

import requests
import json

API_KEY = "YOUR_API_KEY"  # Replace with your actual IPQualityScore API Key
IP_ADDRESS = "93.123.45.10" # Example IP address to check

def check_ip_reputation(api_key, ip_address):
    url = f"https://www.ipqualityscore.com/api/json/ip/{api_key}/{ip_address}"
    params = {
        "strictness": 0, # Adjust strictness level as needed
        "allow_public_access": "true" # Set to 'true' to allow public IP lookups
    }
    try:
        response = requests.get(url, params=params)
        response.raise_for_status()  # Raise an HTTPError for bad responses (4xx or 5xx)
        data = response.json()
        return data
    except requests.exceptions.HTTPError as errh:
        print(f"Http Error: {errh}")
    except requests.exceptions.ConnectionError as errc:
        print(f"Error Connecting: {errc}")
    except requests.exceptions.Timeout as errt:
        print(f"Timeout Error: {errt}")
    except requests.exceptions.RequestException as err:
        print(f"OOps: Something Else {err}")
    return None

if __name__ == "__main__":
    result = check_ip_reputation(API_KEY, IP_ADDRESS)
    if result:
        print(json.dumps(result, indent=4))
        if result.get("fraud_score") > 75:
            print(f"\nWARNING: High fraud risk detected for IP {IP_ADDRESS} with score {result.get('fraud_score')}.")
        else:
            print(f"\nIP {IP_ADDRESS} has a low fraud risk score of {result.get('fraud_score')}.")
    else:
        print("Failed to retrieve IP reputation data.")

This script defines a function check_ip_reputation that constructs the API request URL, includes the API key and IP address, and sends a GET request. It then parses the JSON response and prints relevant fraud detection data. Error handling is included to manage common issues such as network problems or invalid API responses. The fraud_score returned in the JSON payload indicates the likelihood of the IP address being associated with fraudulent activities, ranging from 0 (low risk) to 100 (high risk), as described in the IPQualityScore Fraud Scoring Guide.

Community libraries

As of 2026, the IPQualityScore API primarily relies on direct integration via official code examples rather than widely adopted, community-maintained SDKs in public package repositories. This approach is common for RESTful APIs, where developers often prefer to use generic HTTP client libraries available in their language of choice (e.g., Python's requests, Node.js's axios, Java's HttpClient) and construct API calls directly based on the official API documentation. This method offers developers maximum control and flexibility over their integration, allowing them to tailor the implementation to specific project requirements without being constrained by an SDK's design choices.

While a large ecosystem of third-party community libraries, similar to those found for major cloud providers like AWS SDK for Java or Google API Client Libraries, has not yet emerged for IPQualityScore on platforms like GitHub or npm, developers can still find shared code snippets and discussions on forums like Stack Overflow. These community contributions often provide alternative implementations or extensions to the official examples, addressing specific edge cases or integrating the API within particular frameworks. Developers interested in contributing or finding community-developed tools are encouraged to search public code repositories and developer communities for projects tagged with "IPQualityScore" or "fraud detection API".

The absence of formally maintained community SDKs does not impede integration, given the straightforward nature of the IPQualityScore API's RESTful design. Developers can build their own wrapper libraries or utility functions around the core HTTP calls, effectively creating a custom SDK tailored to their application's needs. This practice is often preferred in enterprise environments where tight control over dependencies and code structure is essential. The official documentation serves as the authoritative source for all API endpoints, parameters, and response formats, ensuring that any custom integration remains compliant and functional with the latest API version.