Point in time snapshot (PIT id), original query required when paging?

I implemented pagination inside an API using point in time snapshots for efficiency. In the first request a PIT is generated and in subsequent requests the PIT is being supplied with the request.

What I would like to do is split the API endpoint into two endpoints. The first endpoint is to get the PIT and the other endpoint is to scroll using the PIT. When looking at Elasticsearch examples the query is always send on subsequent searches together with the PIT.

But is this really necessary? Also what happens if you change the query is subsequent calls? Won't you get inconsistent results???

Point in time locks a version of all documents in the index, not a particular subset of documents from a query. The Lucene index is made up of segment files which never change. New or updated documents are placed in new segments. Deletes add a note about which files in existing segments are to be ignored. Fragmented segments are merged into newer segments (minus the deletes) and the old segments are finally deleted. Point in time simply calls a halt to any purging of a set of old segments and remembers which segments form this required view of the data. Searches on the pit-id only search these old segments while all other "normal" searches look at the newer segment files. When the point in time view is no longer required merging+purging can resume on these older segments.