Expose /page/references endpoint via RESTBase. Basically the same as what was done for /page/metadata and /page/media.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T169242 Develop Page Content Service for Reading Clients | |||
| Resolved | None | T177425 Develop General Layer of PCS | |||
| Resolved | • Jhernandez | T177426 Develop structured JSON APIs for general consumption | |||
| Resolved | • Pchelolo | T189750 Expose new PCS JSON endpoints via RESTBase | |||
| Resolved | • bearND | T190337 Expose /page/references endpoint via RESTBase |
Event Timeline
Comment Actions
It looks like this endpoint and "metadata" are not working.
https://en.wikipedia.org/api/rest_v1/page/summary/Film still lists them under "api_urls", but I don't see them in the swagger docs.
https://en.wikipedia.org/api/rest_v1/page/metadata/Film and https://en.wikipedia.org/api/rest_v1/page/references/Film fail.
Comment Actions
@Halfak See T247991 and its subtask.
TL;DR: the media, metadata, and references endpoints were experimental and have been dropped, but removing those entries from api_urls would be a breaking change to the summary response, which is marked stable. We're in the middle of defining a deprecation policy for both cases.