This document outlines how to access the Armor API system using the Pre-Shared Key (PSK) authentication method. This method applies to all Armor API's.
Create an API key in AMP, and then authenticate through the command line
You can use the API tokenization feature in the Armor Management Portal (AMP) to create an API key. This key will help you log into the Armor API system.
After you create a key, you can use a GET request to log into the Armor API system.
Before you begin:
If you access the Armor API system through an AMP-generated API Key, then you will not be able to access the following endpoints:
- GET /users/{id}/keys
- DELETE /users/{id}/keys/{key}
- POST /users/{id}/keys
- GET /users/{id:int}/ActivationCode
- POST /users/resetpassword
- POST /users/setpassword
- PUT /users/{id:int}
- POST /users/status
- POST /users/
- POST /users/{userId:int}/invite
- GET /users/LockedOut/{accountId}/{email}
- POST /users/unlock/{accountId}/{email}
- DELETE /users/softDelete
- PUT /usersecurity/challengephrase
- GET /usersecurity/securityinformation/{referencekey}
- POST /usersecurity/securityinformation/{referencekey}
- POST /usersecurity/securityinformation/existing/{referencekey}
- GET /usersecurity/challengephrase/{userId}
- POST /usersecurity/validatemfaphone
- POST /usersecurity/securityinformation/{accountId}/{userId}
- POST /usersecurity/validatephoneapppin
Troubleshooting
If you cannot create or access the API Keys screen, consider that:
- You may not have permissions to use this feature.
- You must have the following permissions enabled:
- API Keys All Read
- API Keys All Delete
- API Keys Self Manage
- To learn how to update your permissions, see Roles and Permissions.
- You must have the following permissions enabled: