This is your reference for taking advantage of MetaAccess APIs within your environment. Be sure to reference to the Branding Guidelines as well as the terms and conditions as you develop your applications. Check back often as our APIs are growing to accommodate our user community as well as our platform.
Our Cloud APIs allow developers to easily integrate the data available through our cloud platform into your own applications. This data includes
endpoint details such as device information (Host name, Device ID, MAC/IP Address,...)
device security and compliance status, such as Antivirus, Anti-phishing, Public File Sharing, and Malware detection as well as account information.
These APIs can be used to provide authentication and enforcement via a Secure Access solution (SSL VPN, NAC, etc) or can be integrated into a Remote Monitoring and Management platform for expansive visibility into the endpoints under management. The options are unlimited.
To work with our APIs, you can follow the below steps:
Register your application
Before getting started, you will need to set up a MetaAccess account in order to begin registering your applications to our platform. Follow guideline here to create your account on MetaAccess. Once your account is created, you can proceed with registering your application. Following submission, applications are confirmed and Client Key and Client Secret strings are provided. These keys are unique and should remain confidential.
Before you register your application through the MetaAccess oAuth Portal. You will be expected to provide the following information when registering:
Application description - purpose of the application
Application URL - place where their application resides
Callback URL - where user is redirected after authorizing application for access to the account
Note: Please reference our Branding Guidelines for your application name.
Implement your application
MetaAccess leverages OAuth 2.0* technology, so you should be familiar with the OAuth 2.0 specifications and general flow to ensure that your application is capable of supporting the MetaAccess APIs.
To help you get started with the MetaAccess APIs, we have developed extensive documentation and sample applications. Click here to read more about how to implement with the APIs or to download the sample code.
*OAuth 2.0 is an open protocol used by OPSWAT for authorization of access to resources within our platform. You can read more about OAuth 2.0 here.
You will need to provide a name for your application upon registration. Please note that the name should not include the words “OPSWAT” or “Metadefender Endpoint” or "Gears" or "MetaAccess", or begin with a derivation of those names.
We will need your application’s logo as part of the application registration process. If you change your company name, application name, logo, or website, please let us know by updating your information in the Application portal.
OPSWAT Logo and Guidelines
You are free to use the OPSWAT name and logo in relation to your application, including marketing materials and website content; however we do ask that you follow the OPSWAT guidelines. If there are any questions, please contact the OPSWAT Team.