Support multiple API keys
The v3 API allowed the use of a public API and a private API key. The v4 API only allows the use of the private API key. However, we do not want to disseminate our production private API key to the entire developer staff.
With v3 we defaulted to the public API key to allow developers to work unencumbered while also protecting the more powerful private API key from potential abuse by only having it used in production deployment. No developer has access to production.
The feature request is to either:
1) make v4 API work like v3 API and allow the use of both public and private API key, or
2) allow us to have multiple private API keys so we can use one for development and a different one for production