The endpoints that drive the gateway UI contain very useful information however, if you're using OAuth for authentication, reading this data programmatically is difficult.
For example, ./data/perspective/status/sessions/ has excellent information around sessions, who's using what resources, and there are metrics around scripts, messages and expressions.
It would be great to conveniently read this data, either by an external system, or back-into ignition so that it could be historized.
This way, we can find most intelligently decide where optimizations can be made etc.
API endpoints clearly exist, bolting-on swagger would expose this functionality in a low-effort way.
Lastly, to make this convenient for developers adding an API key method for authentication would be the icing on the cake.
This would assist with the other suggestion of allowing API calls for configuration.