Field | Description | Possible Values |
strictness | How strictly should we scan this URL? Stricter checks may provide a higher false-positive rate. We recommend defaulting to level "0", the lowest strictness setting, and increasing to "1" or "2" depending on your levels of abuse. | integer (0-2) |
fast | The API will provide quicker response times using lighter checks and analysis when enabled. This setting defaults to "false". | boolean, string (true or false) |
timeout | Maximum number of seconds to perform live page scanning and follow redirects. If your implementation requirements do not need an immediate response, we recommend bumping this value to 5. The default value is 2 seconds. | integer (1-10) |
- Proxy & VPN Detection API
- Email Verification API
- Phone Number Validation API
- Device Fingerprint API
- Malicious URL Scanner API
- Mobile Device Fingerprinting SDK
- Gaming Fraud Detection SDK
- Dark Web Leak API
- Malware File Scanner API
- Request List API
- Fraud Reporting API
- Credit Usage API
- Bulk Validation CSV API
- Allowlist & Blocklist APIs
- Plugins Platforms & Integrations
- IP Reputation Database
- Custom Integrations
- Country List API
Advanced Options
Additional Request Parameters
Custom Variables
You can pass custom tracking variables (such as userID and transactionID) established in your account settings with each API request. This allows our reporting tools to filter by specific variables such as users, products, campaigns, and transactions so you can easily match up records with your system to identify fraudulent activity.
Making Requests Without Passing API Key in URL
Due to the nature of platform requirements or frameworks, you may need to request the Malicious URL Scanner API endpoints without passing the API key to the URL. You can alternatively pass the API key via GET, POST, or Headers. These requests use the following endpoints:
JSON
XML
Method | Value | Example |
GET | key | key=YOUR_API_KEY_HERE&url=https%3A%2F%2Fgoogle.com |
POST | key | key=YOUR_API_KEY_HERE&url=https%3A%2F%2Fgoogle.com |
Header | IPQS-KEY (Additional parameters passed as either GET or POST) | IPQS-KEY: YOUR_API_KEY_HERE |