I recently suggested on the Stack Apps site that a formal API be added to SEDE, and it was suggested I reference the feature request here, for visibility.
My use case is a query that the API does not support, so I thought it would be interesting to get it programmatically from SEDE instead. I wonder if this feature might be of interest to others here? This answer outlines the current ways that SE data is available via various APIs and UIs.
I wonder if my use case (retrieving revisions filtered by user) might have been supported by OData, but that's been turned off since April of this year.
This question has sort-of been asked before, back in 2010, though that was not an explicit feature request, and is now rather out of date. It would be good to find out what the current views are on this topic, and indeed whether there is much demand.
My use-case does not urgently require this, since I can use public SE screen scraping or SEDE CSV downloading. From reading around the SE Meta network, both of these approaches seem to be tolerated, as long as it is done with careful regard to frequency and bandwidth.