API:Rollback

POST request to revert the last series of edits made by one user to a given page.

Example
Making any POST request is a multi-step process:

  Log in, via one of the methods described in .   GET a :

  Send a POST request, with the CSRF token, to take action on a page and in this process gain   rights to the given page:

 GET a rollback token:  If your wiki is using MediaWiki 1.24+, follow these instructions:

  Rollback tokens aren't universal: they are not only different for every login, but also depend on the title of the page and the name of the user whose edits are to be rolled back. For MediaWiki 1.23 or earlier, follow these instructions:

</li> </ul> </li> </ol>

POST request
Send a POST request, with a rollback token to revert a user's edits to the Sandbox page.

Response
The Response section below is for the final POST request, to revert the edits to the Sandbox page.

The revision IDs in the response are:
 * <tt>revid</tt>: The ID of the new revision created by the rollback.
 * <tt>old_revid</tt>: The ID of the newest revision being rolled back. Before the rollback, this was the current revision.
 * <tt>last_revid</tt>: The ID of the revision being restored by the rollback. This is the newest revision having been rolled back.

Sample code
rollback.py

Permissions
Rollback requires both the <tvar|1> </> and the <tvar|2> </> right on the target page; currently, this means that OAuth consumers, bot passwords etc. require both the <tvar|1> </> and the <tvar|2> </> grant – <tvar|2> </> alone is not enough!

Possible errors
In addition to 1>Special:MyLanguage/API:Errors#Standard error messages</>|the usual stuff:

Parameter history

 * v1.24: Introduced <tvar|1> </>
 * v1.27: Introduced <tvar|1> </>
 * v1.17: Introduced <tvar|1> </>

Additional notes
Optionally, both the rollback and the edits being rolled back can be marked as bot, which hides them from Special:RecentChanges by default.