API:Wikimania 2006 API discussion
|This MediaWiki page is inactive and kept for historical interest. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date.|
A simple-as-possible API was quickly designed at the Wikimania Hacking Days on 4 August 2006. This minimal API only supports the most essential functions, with the goal of allowing a quick implementation, with other functionality (moving pages, uploading images, etc.) to be specified once a basic API has been implemented.
Login[edit | edit source]
This function logs the user into mediawiki using a username and password. Other authentication methods could possibly be added in the future.
- username, password, (API key)
- API key is not needed but should be introduced now, as it would make it very difficult to get it in later. --Yurik 14:52, 6 August 2006 (UTC)
- success, authentication failure, or temporary failure
- We can use standard HTTP error codes (500-something is a security error, 200ish - accept, need to lookup the exact codes). --Yurik 14:52, 6 August 2006 (UTC)
Retrieving Data[edit | edit source]
Please note that a much more extensive interface - Query API is already available for all media wiki servers. It allows developers to minimize the server load and bandwidth consumption by returning only the data specifically requested. By total coincidence the usage is similar to what Yahoo just released at python dev center.
read revision[edit | edit source]
This function requests the full text of a single article revision, either by article title/page ID, in which case the most recent revision is fetched, or by revision ID. The return value is xml which includes the name of the page, the name of the most recent editor, a revision ID and timestamp, the full wikitext of the revision, and a flag if the article is a redirect, including the name of the page to which it redirects.
- article title or page ID, or revision ID
- A format mostly identical to the current special:export, but also including some metadata about whether the page is a redirect, and the page to redirect to, so that the client does not need to parse the wikitext
Each property requested in the what=... incures additional performance penalty, some more than others.
- in article title, with redirect info
- in article ID, with redirect info
- in revision ID, with redirect info
- in article title
- in article ID
- in revision ID
read history[edit | edit source]
This function requests the edit history of an article, referenced either by title, or by page ID. The range start parameter determines the first edit returned, referenced by revision ID or ISO date. The limit parameter determines how many pages before or since that edit should be in the list, up to 5000 revisions, or some other maximum to be determined.
- article title or page ID, range start, +- limit
- range start can be ISO date or revision ID.
- if negative range start, fetch last limit revisions bounded by some maximum of revisions: currently 5000
- always return up to 5000 revisions
- export xml metadata (see readrevision)
return 10 revisions standard, more revisions will be returned when the rvlimit=? parameter is added
- in article title
- in page ID
Submitting Data[edit | edit source]
This function attempts to save an article to the mediawiki server. The revision ID of the revision the edit is based on is provided so that in the case of an edit conflict, the function will fail. If another edit has been made to the page since the page was loaded, but a simple merge is possible, then the function will succeed.
- last revision ID or 0 (if the page is new), page text, page title, edit comment, minor edit flag, edit token
- success(version ID), edit conflict fail, permission failure, temp failure
Notes[edit | edit source]
- UTC only, ISO 8601
- Date = 0 means the current revision
Simple merges on write:
- Because simple merges will be undertaken automatically by mediawiki, it is impossible to assume that when the write article function succeeds, the submitted text is authoritative. If further edits will be made, a new copy of the most recent revision should be fetched from the server.