IPQualityScore's bulk malicious URL scanner validation API allows you to upload a large list of URLs or domains for batch processing through our URL scanner API service. This guide will focus on uploading data in a JSON format, but you're free to use any of our available upload methods, such as POST file upload or a remote file URL.
Uploading CSV files to be processed by our system occurs in a series of steps. Each step is briefly discussed below and additional documentation is available on each step on the left menu. The example script on this page can be used as a quick guide for uploading an URL or domain list for processing. Other upload methods are also available. If you have questions on how to implement this system, please feel free to reach out to our support team and we'll be happy to assist.
Start by making a POST request containing URLs (and potentially other data points, see our Malicious URL Scanning API documentation for more information on allowed parameters) to the API URL described below. A few headers are also required to make this request work. Once you've uploaded the request to our servers you should get a response similar to our success example below.
Headers | |
---|---|
Field | Value |
Content-Type | application/json |
JSON Body / Data |
---|
|
For example success/failure responses check out our extended uploading a CSV documentation. You should be able to grab the status URL (or ID) from the response and use that for Step 2.
Your CSV will start processing after upload. Depending on the size of your CSV, processing may take a while to complete. You will want to periodically check the status of your CSV's processing by calling our status API. Here's an example call.
Once your CSV's status returns FINISHED you can then access any download links supplied to retrieve the output file. Results will be in CSV format.
Please consult the Malicious URL Scanner API documentation for further details on each data point's definition. This page explains best practices for using our URL Scanner API along with a detailed description of the API's retuned data points.