Good idea, Dan. One thing I might suggest is to have the query parameters reflect the fact that there are multiple resources under each connector. There is `connectors/<name>/`, `connectors/<name>/config`, and `connectors/<name>/status`. Each of them returns a slightly different set of information, so it would be useful to allow the query parameter be a string instead of a true/false flag. In this case, `expand=status,config` would specify expanding both the /status and /config subresources into the response objects.
Other than this detail, I think this is a useful addition to the Connect REST API. Alex
