Currently, it appears only a single organizational API key can exist at any given time. It would be nice to have the ability to generate multiple API keys and name them based on how they're being used.

Related, having created, created by, expiration (optional), "last used" and "last seen" would be useful when managing multiple keys.

This might also be a prerequisite to supporting a related request - scoping of API keys to specific tenants (https://feedback.huntress.com/huntress-api/p/msp-breakdown-of-api-access).