Topic on Talk:Page Previews/API Specification

Rightly or wrongly, we're looking to make the new service's response consistent with the existing summary API.

Shouldn't responses be consistent with the existing summary API?

This way no client side changes are needed and the new endpoint will be interchangeable with the rest base summary API...

Not necessarily, no. This spec revolved around the idea that RESTBase's ability to version APIs was easy and cheap. We now know that the former is true but the latter isn't. It'd be foolish to believe that the APIs are actually the same (both semantically and in terms of their content) but it's what we have to do to minimise the const of getting the new service exposed in production…