API:Extensions/en

This document covers creating an API module in an extension for use with MediaWiki 1.30 and later.

Module creation and registration
All API modules are subclasses of, but some types of modules use a derived base class. The method of registration also depends on the module type.
 * action modules : Modules that provide a value for the main  parameter should subclass . They should be registered in   using the   key.
 * format modules : Modules that provide a value for the main  parameter should subclass . They should be registered in   using the   key. It's very uncommon for an extension to need to add a format module.
 * query submodules : Modules that provide a value for the,  , or   parameters to   should subclass  (if not usable as a generator) or  (if usable as a generator). They should be registered in   using the  ,  , or   key.

In all cases, the value for the registration key is an object with the module name (i.e. the value for the parameter) as the key and the class name as the value. Modules may also be registered conditionally using the ApiMain::moduleManager (for action and format modules) and ApiQuery::moduleManager (for query submodules) hooks.

Prefix
In the constructor of your API module, when you call  you can specify an optional prefix for your module's parameters. (In the generated documentation for a module this prefix, if any, appears in parentheses in the heading for the module.) If your module is a query submodule then a prefix is required, since a client can invoke multiple submodules each with its own parameters in a single request. For action and format modules, the prefix is optional.

Parameters
Most modules require parameters. These are defined by implementing. The return value is an associative array where keys are the (unprefixed) parameter names and values are either the scalar default value for the parameter or an array defining the properties of the parameter using the  constants defined by.

The example illustrates the syntax and some of the more common  constants.

Parameters are documented using MediaWiki's i18n mechanism. See #Documentation for details.

Execution and output
The code actually implementing the module goes in the method. This code will generally use to get the input parameters, and will use  to get the  object to add any output to.

Query prop submodules should use to access the set of pages to operate on.

Query submodules that can be used as generators will also need to implement which is passed an  that should be filled with the generated pages. In this case, the  should generally not be used.

Caching
By default API responses are marked as not cacheable ('Cache-Control: private')! For action modules, you can allow caching by calling. This still requires clients pass the  or   parameters to actually enable caching. You can force caching by also calling.

For query modules, do not call those methods. You can allow caching by instead implementing.

In either case, be sure that private data is not exposed.

Token handling
If your action module changes the wiki in any way, it should require a token of some kind. To have this handled automatically, implement the  method, returning the token that your module requires (probably the   edit token). The API base code will then automatically validate the token that clients provide in API requests in a  parameter.

Master database access
If your module accesses the master database, it should implement the  method to return.

Returning errors
includes several methods for performing various checks, for example,
 * If you need to assert that exactly one of a set of parameters was supplied, use.
 * If you need to assert that at most one of a set of parameters was supplied, use.
 * If you need to assert that at least one of a set of parameters was supplied, use.
 * If you need to assert that the user has certain rights, use.
 * If you need to assert that the user can take an action on a particular page, use.
 * If the user is blocked (and that matters to your module), pass the  object to.

But you will often run into cases where you need to raise an error of your own. The usual way to do that is to call, although if you have a  with the error information you could pass it to  instead.

If you need to issue a warning rather than an error, use, or if it's a deprecation warning.

Documentation
The API is documented using MediaWiki's i18n mechanism. Needed messages generally have default names based on the modules "path". For action and format modules, the path is the same as the module's name used during registration. For query submodules, it's the name prefixed with "query+".

Every module will need a  message, which should be a one-line description of the module. If additional help text is needed,  may be created as well. Each parameter will need a  message, and parameters using   will also need a   for each value.

More details on API documentation are available at.

Extending core modules
Since MediaWiki 1.14, it's possible to extend core modules' functionality using the following hooks:


 * APIGetAllowedParams to add or modify the module's parameter list
 * APIGetParamDescription to add or modify the module's parameter descriptions
 * APIAfterExecute to do something after the module has been executed (but before the result has been output)
 * Use APIQueryAfterExecute for,   and   modules
 * If the module is run in generator mode, APIQueryGeneratorAfterExecute will be called instead

List of extensions with API functionality
See API extensions for examples of extensions that add to or extend the API.

Testing your extension

 * Visit [/api.php api.php] and navigate to the generated help for your module or query submodule. Your extension's help information should be correct.
 * The example URLs you provided in  should appear under "Examples", try clicking them.
 * Omit and mangle URL parameters in the query string, check your extension's response.
 * Install and interactively explore your API.
 * Visit to see additional information about your extension.