|Language:||English • Deutsch • español • français • Bahasa Indonesia • 日本語 • 한국어 • русский • українська • 粵語 • 中文 • 中文（台灣）|
- This is an introductory overview. See the menu bar on the right for more detailed sub-topics.
On new MediaWiki installations, the web service is enabled by default, but an administrator can disable it.
MediaWiki has two more outward-facing interfaces:
- The Special:Export page, which provides bulk export of wiki content as XML. Read the Export help article on meta.wikimedia.org for more information.
- The standard web-based interface (which you are likely using right now). Read Manual:Parameters to index.php for information on using the web-based interface.
A simple example
This URL tells English Wikipedia's web service API to send you the content of the main page:
Use any programming language to make an HTTP GET request for that URL (or just visit that link in your browser), and you'll get a JSON document which includes the current wiki markup for the page titled "Main Page". Changing format to jsonfm will return a "pretty-printed" HTML result good for debugging.
Let's pick that URL apart to show how it works.
This is the endpoint. It's like the home page of the Mediawiki web service API. This URL is the base URL for English Wikipedia's API, just as
http://en.wikipedia.org/wiki/ is the base URL for its web site.
If you're writing a program to use English Wikipedia, every URL you construct will begin with this base URL. If you're using a different MediaWiki installation, you'll need to find its endpoint and use that instead. All Wikimedia wikis have endpoints that follow this pattern:
http://en.wikipedia.org/w/api.php # English Wikipedia API http://nl.wikipedia.org/w/api.php # Dutch Wikipedia API http://commons.wikimedia.org/w/api.php # Wikimedia Commons API
Since r75621, we have RSD discovery for the endpoint: look for the
link rel="EditURI" in the HTML source of any page and extract the
api.php URL; the actual link contains additional info. For instance, on this wiki it's:
<link rel="EditURI" type="application/rsd+xml" href="//www.mediawiki.org/w/api.php?action=rsd" />
Otherwise, there's no safe way to locate the endpoint on any wiki. If you're lucky, either the full path to index.php will not be hidden under strange rewrite rules so that you'll only have to take the "edit" (or history) link and replace index.php (etc.) with api.php, or you'll be able to use the default ScriptPath (like
Now let's move on to the parameters in the query string of the URL.
This tells the Wikimedia web service API that we want data to be returned in JSON format. You might also want to try
format=jsonfm to get an HTML version of the result that is good for debugging. Even though the API supports many different output formats such as WDDX, XML, YAML and native PHP, there are plans to remove all formats except for JSON, so you might not want to use them.
This is the 'action'. The MediaWiki web service API supports over fifty actions, and they're all documented in the API reference. In this case, we're using "query" to tell the API that we want to get some data.
The "query" action is one of the API's most important actions, and it has extensive documentation of its own. What follows is just an explanation of a single example.
The rest of the example URL contains parameters used by the "query" action. Here, we're telling the web service API that we want information about the Wiki page called "Main Page". (The %20 comes from percent-encoding a space.) If you need to work with multiple pages, please consider putting them all in one request to optimize network and server resources:
titles=PageA|PageB|PageC. See the query documentation for details.
This parameter tells the web service API that we are interested in a particular revision of the page. Since we're not specifying any revision information, the API will give us information about the latest revision — the main page of Wikipedia as it stands right now.
Finally, this parameter tells the web service API that we want the content of the latest revision of the page. If we passed in
rvprop=content|user instead, we'd get the latest page content and the name of the user who made the most recent revision.
Before you start using the MediaWiki web service API, be sure to read these documents:
- The FAQ.
- The page about input and output formats
- The page about errors and warnings
Beyond that point, what you need to read depends on what you want to do. The right-hand menu links to detailed, task-specific documentation, and some more general guidelines are given below.
Identifying your client
When you make HTTP requests to the MediaWiki web service API, be sure to specify a
User-Agent header that properly identifies your client. Don't use the default
User-Agent provided by your client library, but make up a custom header that identifies your script or service and provides some type of means of contacting you (e.g., an e-mail address).
An example User-Agent string might look like:
MyCoolTool/1.1 (http://example.com/MyCoolTool/; MyCoolTool@example.com) BasedOnSuperLib/1.4
On Wikimedia wikis, if you don't supply a
User-Agent header, or you supply an empty or generic one, your request will fail with an HTTP 403 error (cf. m:User-Agent policy). Other MediaWiki installations may have similar policies.
User-Agent header: the browser will use its own. There is currently no other mechanism for a browser-based client to identify itself.
In PHP, you can identify your user-agent with code such as this:
ini_set('user_agent', 'MyCoolTool/1.1 (http://example.com/MyCoolTool/; MyCoolTool@example.com) BasedOnSuperLib/1.4');
Or if you use cURL:
curl_setopt($curl, CURLOPT_USERAGENT, 'MyCoolTool/1.1 (http://example.com/MyCoolTool/; MyCoolTool@example.com) BasedOnSuperLib/1.4');
Your client will probably need to log in to MediaWiki, possibly via its own user account. See the login manual page for details.
Please also read: API:Etiquette
Per the HTTP specification, POST requests cannot be cached. Therefore, whenever you're reading data from the web service API, you should use GET requests, not POST.
Also note that a request cannot be served from cache unless the URL is exactly the same. If you make a request for
api.php?....titles=Foo|Bar|Hello, and cache the result, then a request for
api.php?....titles=Hello|Bar|Hello|Foo will not go through the cache — even though MediaWiki returns the same data!
You should take care to normalize the URLs you send to the MediaWiki web service, so that slightly different user input won't cause you to waste time on unnecessary HTTP requests. You can normalize a list of page titles by removing duplicates and sorting the titles alphabetically. Similar techniques will work for other kinds of data.
The menu bar on the right side of this page links to more detailed, task-specific documentation. Here are some links having to do with the API as a whole:
- The API sandbox available on all Wikimedia wikis makes it easy to try out different actions interactively.
- The API reference contains automatically-generated descriptions of all actions and parameters.
- Hook into Wikipedia information using PHP and the MediaWiki API (IBM developerWorks article, 17 May 2011)
- Hook into Wikipedia using Java and the MediaWiki API (6 April 2012)
- The API tutorial leads you through hands-on exercises and includes a training video.
- Mailing list for notifications and questions: API mailing list
- Low-traffic mailing list for announcements only (all posts to this list are posted to mediawiki-api as well): mediawiki-api-announce
- View and report API bugs: Bugzilla (When reporting new bugs, don't forget to set Component=API)
- Browse the API source code
- The current MediaWiki database schema
- Browse the current database schema in git