These APIs are marked as BETA for feedback. We may not be able to keep backward compatibility until it is officially released.
This chapter describes the REST API calls that can be used with MetaDefender Vault. Through the Application’s Interface, any 3rd party application can interact and communicate directly with MetaDefender Vault. This allows you to add MetaDefender Vault to your automated workflow. Each call should include an authentication token or user credentials (username and password) or use API Tokens.
About this REST API
All endpoints require you to provide the Authorization header. The value for this header should be obtained by calling Request An Authentication Token. Please note that an authentication token has a limited lifetime and it should be refreshed to avoid expiration policy.
In order to change the URL it is recommended to use the Protocol Configuration Tool (located by default in C:\Program Files\OPSWAT\MetaDefender Vault\Tools).
This URL can also be changed directly from the configuration file by following these steps:
Go to the installation directory (by default C:\Program Files\OPSWAT\MetaDefender Vault)
Navigate to the WebServer/conf folder
Open the file called dynamic.conf using administrative privileges
Edit the following section of the configuration file as you wish:
Or, in case of TLS/SSL:
listen <ip_address>:<port> ssl;
Restart MetaDefender Vault Helper Service (vaultHelper) for changes to apply.
Sample Postman Collection
Some of the REST APIs have been exported in the following collection that you can download and try: OPSWAT MetaDefender Vault Postman Collection.json