You make a POST request to https://api.armis.com/v3/oauth/token. See more details here.

The API ref page of each endpoint declares the required scopes. For example, in the API ref page of the /assets/_bulk endpoint, you can see that the required scope is PERMISSION.DEVICE.MANAGE.EDIT. Alternatively, when you make an API call without the right scopes, the error message from the server will let you know exactly which scopes are missing, for example: The token is not authorized to access this resource. Missing scopes PERMISSION.DEVICE.MANAGE.EDIT

You can use the data-export functionallity which is documented here.

You can follow the check list that we curated exactly for this purpose. Note, that should you want to be officialy certified by Armis, this check list becomes a requirements list.

Yes, we have a Python SDK. However, its content is rather limited at the moment. You can read the documentation here.

API v3 is the latest iteration of our API. It brings enhancements to the old APIs (v1 and v2) in security, simplicity, consistency, and documentation. We acknowledge that not everything that can be done in v1 and v2 can be done in v3. If you're missing some key functionality from v1 or v2, please raise the topic in the discussions page.

Yes, you can use the same secret key for authenticating both v1 and v3. However, the authentication mechanism is different - head to the authentication guide for details.

You can access the documentation and API reference for v1 and v2 only if you have access to an Armis Centrix tenant. In that case, go to Settings > API Management, and there you'll find links to "API Docs" (i.e. API reference) and "API Guide" (i.e. documentation).

If you arrived here following a request from a mutual customer (or a prospect), please reach out to them for credentials for their tenant.

You can find them here.

Yes, you can get the Integration Certification.