Add an indicator to the scanning queue and receive a queue ID, so you can poll for results.
Your Pulsedive API key.
API key authentication is optional. However, requests without a key have stricter rate limits. We recommend including an API key for better performance and reliability.
Value of the indicator to scan. May be:
microsoft.com)8.8.8.8)https://pulsedive.com/explore)To use a base64-encoded indicator, use the ioc parameter instead.
Base64-encoded value of the indicator to scan.
Useful for safely transmitting indicators that contain special characters or when the indicator is not being processed correctly through the indicator parameter. (If this is happening, please let us know.)
Use this parameter instead of indicator when submitting base64-encoded data.
Scan type for the indicator.
Passive scans collect data without direct contact, such as through WHOIS and DNS requests. Active scans include port scanning and web browser analysis, which are more detectable.
For active scanning, set to 1.
For passive scanning, set to 0.
0, 1 Controls whether to save the scanned indicator to Pulsedive's database.
To store the indicator and make it searchable in future queries, set to 1.
To scan and enrich without storing, set to 0.
If you scan an indicator that already exists in the database, Pulsedive updates it with fresh scan results regardless of this parameter's value.
0, 1 Indicates whether to format returned JSON results.
For pretty-printed output, set to 1.
For compact output, set to 0.
0, 1 Successful request. Returns scan queue information in JSON format.
Unique identifier of the scan request (Queue ID).
"2100254203"
Dynamic key-value pair representing the outcome of your request.
Each {key} represents the overall outcome of your request. The {value} string provides additional context for the outcome. Until your request is complete, the {key} will be error.
{ "error": "Added request to queue." }