Supported API methods in KAV protocol version 3

March 5, 2024

ID 181169

The following table lists the API methods that Kaspersky Scan Engine supports in HTTP mode when using KAV protocol version 3. The format of the requests does not depend on whether the client uses TCP or UNIX sockets for interaction with Kaspersky Scan Engine.

API methods supported in HTTP mode in KAV protocol version 3

API method

HTTP method

Format

Description

/api/v3.0/scanfile

/api/v3.1/scanfile

POST

Request format

Scans a file.

Use the /api/v3.1/scanfile API method to get more information about the scanning process.

/api/v3.0/scanmemory

/api/v3.1/scanmemory

POST

Request format

Scans a block of system memory.

Use the /api/v3.1/scanmemory API method to get more information about the scanning process.

Use only the KAV_SKIP cleaning mode when scanning system memory. Kaspersky Scan Engine cannot disinfect or delete files in this mode.

/api/v3.0/checkurl

POST

Request format

Checks a URL.

/api/v3.0/basesdate

GET

Request format

Gets the release date of the anti-virus database. You can use this method to check whether kavhttpd is running.

/api/v3.0/version

GET

Request format

Gets the current version of KAV SDK. You can use this method to check whether kavhttpd is running.

/api/v3.0/licenseinfo

GET

Request format

Gets information about the current key file or activation code. You can use this method to check whether kavhttpd is running.

/api/v3.0/getstatistics

GET

Request format

Gets the accumulated statistics.

/api/v3.0/clearstatistics

POST

Request format

Clears the accumulated statistics.

/api/v3.0/update/start

POST

Request format

Updates the anti-virus database.

/api/v3.0/update/status

/api/v3.1/update/status

GET

Request format

Gets the status of the database update process.

Use the /api/v3.1/update/status API method to get more information about the database update process.

/api/v3.1/ksninfo

GET

Request format

Gets the information about KSN.

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.