Native management API
BotConnector's account, billing, device, admin, and Workspace management routes are internal application surfaces. They are not part of the public Hosted Developer API contract, and no client should be built against them.
That is a deliberate boundary rather than a missing feature: those routes move whenever the application's own screens change, which is far more often than an API a customer depends on should.
Where those actions live
Use Workspace for anything about the account itself:
- API keys — create, list, and revoke
- Usage and the model catalogue for your plan
- Billing state and plan changes
- Integrations and connected devices
For inference, use the Hosted Developer API. That page is the authoritative list of routes that are public today.
The old local management API
The local native management API belonged to the legacy managed-runtime preview. It is not the current public contract, and new local work goes through the CLI and the local runtime instead — see Network boundary for which addresses are current.
If you need something that is not here
If your integration needs a capability that only an internal route would provide, that is a feature request rather than a workaround opportunity. Build against the public routes and use Workspace for account operations; an integration resting on an internal route will break quietly the next time the application ships.