Managing API Keys

An Application Programming Interface (API) integrates with the 802 Secure cloud environment to provide programatic access to collected data. Event data can be retrieved and forwarded to additional logging platforms and SIEMs to provide further integration with an existing operations and monitoring environment.

API keys allow programmatic access to the 802 Secure Console API from applications. This access is a limited subset of features from the primary console. They include:

• Creation and retrieval of Events/Alerts
• Retrieval of Clients or AccessPoints identified within a date range
• Retrieval of AccessPoint details via BSSID or unique identifier
• Retrieval of Client details via MAC Address or unique identifier
• AirShield Sensor status

Managing API Keys

API Keys are managed on the Customer API Key page accessible from the top right dropdown:

A list of created API Keys is displayed allowing deleting, editing and creating new keys.

Creating API Keys

When created, two types of keys are provided - a string-based authentication key and an ECDSA signature key. ECDSA signing keys are only required for write events such as Event creation and can be ignored if not necessary.

The ECDSA keys are locally generated and can be downloaded from the creation/edit page during your currently logged in session only. After logging out the signing key cannot be retrieved and must be re-generated. ECDSA verification keys can be replaced with your own verify keys if desired.

Press the Plus button at the top right of the API Key list to create a new key. The Edit API Key will load providing the Key ID, a field for user description and the ECDSA Verification Key. At this point you should download the Signing Key and store it for future use. Alternatively you may replace the Verify Key with your own generated data. The Signing key only persists during the current log on and cannot be retrieved after logoff.