Advanced corpus search


Quota consumption

This endpoint consumes VirusTotal Intelligence quota.


Special privileges required

This endpoint is only available for users with special privileges.

This endpoint allows to search for files in the VirusTotal's dataset, using the same query syntax that you would use in the VirusTotal Intelligence user interface. URL Safe encoding must be used when using this endpoint programatically.

The result from this endpoint is a collection of file objects that match the given query. If the descriptors_only parameter is set to true, the resulting collection will contain only the object descriptors. This is useful if you are interested in getting only the SHA-256 of the matching files. In those cases you better set descriptors_only=true for reducing the latency of your requests.


Content searches can not be sorted

If your query contains content search the order parameter will make no effect.

The order parameter defines the order in which results are returned. They can be followed by a plus (+) or minus (-) sign for indicating ascending or descending order respectively (i.e: <order>+, <order>-). If no ascending/descending order is specified it's assumed to be ascending, so <order> and <order>+ are equivalent. If the order parameter is not provided, items are returned in a default order. The following table shows supported and default orders for every kind of entity:

Entity type

Supported orders

Default order


first_submission_date, last_submission_date, positives, times_submitted, size



first_submission_date, last_submission_date, positives, times_submitted, status



creation_date, last_modification_date, last_update_date, positives



ip, last_modification_date, positives


This request returns a list of API objects (files, URLs, IP addresses or domains) with no context attributes. Context attributes are only added when searching files by content. These context attributes are:

  • confidence: <float> match confidence.
  • match_in_subfile: <boolean> whether the content match was found in a subfile or not.
  • snippet: <string> snippet ID. This ID can be later used in /intelligence/search/snippets/{id} endpoint.
  "data": [
      "context_attributes": {
        "confidence": 1,
        "match_in_subfile": false,
        "snippet": "L3Z0c2FtcGxlcy8zODIzMzkzNjNhOTM2NDM2ZDM2MDM1MzFkM2IzOGEzMmUzMTUzNzM3MTM4MzY3MzBlM2Q2MzQ4MzY1M2MzYzNhfHw3MTg1Mzk2OjExfHwxNTk5NDY0OTQ3fHwzODIzMzkzNjNhOTM2NDM2ZDM2MDM1MzFkM2IzOGEzMmUzMTUzNzM3MTM4MzY3MzBlM2Q2MzQ4MzY1M2MzYzNh"
      "id": "382339363a936436d3603531d3b38a32e315373713836730e3d63483653c3c3a",
      "type": "file"
  "links": {
    "next": "",
    "self": ""
  "meta": {
    "cursor": "H4sIAAA...",
    "days_back": 365
Click Try It! to start a request and see the response here!