Get an entry’s history, at its history page’s address
The entry’s public revision history as its history page shows it: newest first, 50 to a page, by page number. GET /api/v1/entities/{vhid}/history gives the same revisions with limit and offset instead. An old name redirects (301) to the same address under the entry’s canonical key, query kept. A merged entry’s key answers with that entry’s own history, and merged_into names the entry it became. An entry whose history has been hidden answers 403 history_hidden, saying how to ask for it through the contact page.
Same-origin only: it sends no CORS headers. A key is not needed. One that is sent is checked: a bad one is refused (400 or 401) before the route runs, and a good one makes the answer private (Cache-Control: no-store, Vary: Authorization).
Request
- Base URL: https://verifiedhandles.org
- URL: https://verifiedhandles.org/{key}/history.json
- Auth: one of:
- none
- HTTP bearer
Path parameters
The entry’s VHID (11 digits), its short name, or one of its old names. Short names are matched exactly.
Query parameters
The page, from 1 to 201: the list reads no further than its first 10,000 revisions, as GET /api/v1/entities/{vhid}/history does. Anything below 1 or non-numeric reads as 1; a page past 201 answers as page 202, with an empty history and hasMore false.
Response
A page of the history.
Changes
No recorded changes to this operation across all 1 revision of this API.