Announcing API version 2.1

The scanii team is proud to announce two exiciting new features:

1. Custom file metadata support in API version 2.1

Finally delivering one of our most requested features, version 2.1 of our API now supports user-supplied arbitrary metadata (in the form of simple key/value pairs), for example:

$ curl -i -u 8eb05c68f386421db2dd4929fc4f77ad:12345678 -F metadata[filename]=suba002.exe -F file=@suba002.exe
HTTP/1.1 100 Continue

HTTP/1.1 201 Created
Access-Control-Allow-Headers: Authorization
Access-Control-Allow-Origin: *
Content-Type: application/json
Date: Sat, 12 Dec 2015 17:34:10 GMT
X-Runtime: 1245ms
X-Scanii-Host-Id: 86ddeebc
X-Scanii-Request-Id: ec9a8d74-823b-457f-bdf8-0836c47f7534
Content-Length: 333
Connection: keep-alive

  "id" : "4d323e37433a76d59a78a97d5265ad67",
  "checksum" : "edbb54821bc3f5666be48184a822c3df59392c31",
  "content_length" : 1579562,
  "findings" : [ "" ],
  "creation_date" : "2015-12-12T17:34:12.031Z",
  "content_type" : "application/x-msdownload",
  "metadata" : {
    "filename" : "suba002.exe"

In the example above we took advantage of Scanii's custom metadata ability to store the file name with the content processed. Arguments sent us in the format metadata[key]=value get automatically saved with the resource and it is a great place to store your business logic such as the internal id of the content or the name of the web server (or application) that generated the request.

For more information see API v2.1 Overview

2. Detailed file processing logs

Another exciting feature is the addition of detailed logs to all files processed. You now can use those logs to track down failed callbacks or content download issues and get significantly more insight into how your content was processed.

As always, we would love to hear from you, just shoot us an email at,

The Scanii Team.

Last updated on 01/17/2016.