If this is documented somewhere, please point me to it, but I haven't been able to find answers to these questions.
It seems that API keys can only be created by a user for their own use. Is that true, or is there a way to create and manage API keys at an organization level?
My primary reason for asking is that a deployment of our company's application in the cloud doesn't correspond with an individual Telnyx user -- it's a service. If we deploy with a key tied to a specific user, that precludes other sysadmins from rotating the key, and it's a problem if the user leaves the company. We could create a fake user solely for managing our "service" keys, but that requires sharing the fake user's credentials amongst ourselves and adds tedium.
Is there a way for an admin/owner in the Telnyx account to supervise members' API key usage, and especially to deactivate keys?
Is there a way to scope an API key to a specific set of resources, for example to have separate keys for different deployments of our application?
Basically we need a development key that grants access to our development SIP trunk and DIDs, another for staging trunk and DIDs, and another for production. A key that we use in our development environment to experiment with features shouldn't be allowed to inadvertently modify our production trunk, etc. How can we accomplish this?
EDIT: Numbering and formatting.