2. File Scanning

Overview

Scanning a file starts with uploading the file to MetaDefender Cloud to initiate the scan process. Although we are trying to keep scanning very fast, scanning with more than 30 engines might take from a few seconds to many minutes depending on file type, file size, and current traffic. Also, archives usually take longer when scanning all the files inside. Due to these many variables, we are not able to guarantee scanning times.

Free API users are sent to different queues with a lower priority, and MetaDefender Cloud customers' scan requests are prioritized.

Scanning a file consists of the following steps:

  1. Initiate scan request by uploading a file

  2. Retrieve scan report using unique data_id returned from Scan File API

If a file was already scanned before, uploading a file from the API does initiate a scan. Looking up scan results using a hash value is much faster while using minimum network bandwidth usage compared to uploading a file. Therefore, it is strongly recommended to do a "HASH LOOK UP" before "SCAN A FILE".

If the file was scanned before, and the results are older than 7 days, it is strongly recommended to do a "FILE RESCAN" if the "rescan_available" field is true. File rescan saves bandwidth because the file does not need to be uploaded again.

In order to rescan a file that was scanned before, you can initiate a rescan request using a unique file_id. Please note that file_id is not available for every scan result if it was scanned via private API.

Read more about file scanning APIs: