An Endpoint to Retrieve JSON for a Single Feature

[jpmedley]

Is your feature request related to a problem? Please describe. There is no way other than screen scrapes for consumer of MDN get and display data for a single status entry.

Describe the solution you'd like An end point that I can pass an ID to and get back just the data related to that ID>

Additional context Much information that is currently displayed in articles about new features on developer.chrome.comm, is hand-curated despite being available from Chrome Status. Updating it requires a PR. If a widget could retrieve data about a single Chrome Status entry, then status information about Chrome features could be updated in a place that's available to everyone and with much less effort than is required by a PR.

Whether features.json should be available is out of scope.

[jpmedley]

cc: @tomayac

[jpmedley]

There was a similar request in #2585 (now closed).

Is your feature request related to a problem? Please describe.

I'd like to use feature URLs like https://chromestatus.com/feature/6577673212002304 as the identity of a feature, and then extract information from them in spreadsheets. Unfortunately, curl https://chromestatus.com/feature/6577673212002304, and the similar operation done by spreadsheet functions like IMPORTXML(), doesn't see any of the actual data.

Describe the solution you'd like

Either have the feature page link to a machine-readable expression of its content, or render the content to light-DOM server-side so that an XPath expression can find important fields.

[jyasskin]

I actually found an endpoint for this by inspecting the network requests made by the new Lit frontend. It's at https://chromestatus.com/api/v0/features/6577673212002304. It embeds a leading )]}' (why?), but a custom parser can strip that off.

[jyasskin]

The remaining issue is that the endpoint isn't documented for other tool authors to find.