API:Data formats/es

From MediaWiki.org
Jump to navigation Jump to search
This page is a translated version of the page API:Data formats and the translation is 28% complete.

Other languages:
Deutsch • ‎English • ‎dansk • ‎español • ‎français • ‎polski • ‎português do Brasil • ‎română • ‎русский • ‎українська • ‎বাংলা • ‎ไทย • ‎中文 • ‎日本語 • ‎한국어


The API takes its input through parameters provided by the query string, or from a POST entity in application/x-www-form-urlencoded or multipart/form-data format. Every module (and every action=query submodule) has its own set of parameters, which are listed in the documentation and in action=help. They can also be retrieved through action=paraminfo .


All input should be valid UTF-8, in NFC form. MediaWiki will attempt to convert other formats, which may result in an error.

Multivalue parameters

Some parameters take multiple values, separated by a pipe character (|). For example, to submit the three values red, green, and blue for the parameter color, you would put color=red|green|blue in the query. Whether a parameter accepts multiple values is listed explicitly in action=paraminfo and action=help. The documentation does not distinguish multivalue parameters explicitly, but the descriptions for these parameters are usually along the lines of "A list of ..." or "A pipe-separated list of ...".

If you need to submit a list of values where some of the values contain a pipe character (which should be rare - most multivalue parameters are lists of page titles or usernames, neither of which can contain pipes), you can use the unit separator character instead: color=<US>r|ed<US>gr|een<US>bl|ue (where <US> stands for U+001F) will submit the three values r|ed, gr|een and bl|ue. (Note that there is an extra <US> at the beginning. This is mandatory to avoid ambiguity around submitting a single value containing a pipe.)

Valores booleanos

Boolean parameters work like HTML checkboxes: if the parameter is specified in the HTTP request, regardless of value, it is considered true. For a false value, omit the parameter entirely. The best way to specify a true parameter in an HTTP request is to use someParam=; the trailing = ensures the browser or HTTP library does not discard the "empty" someParam.


Parameters that take timestamp values accept multiple timestamp formats:

  • Formato ISO 8601: 2008-08-23T18:05:46Z
  • MediaWiki's internal timestamp format : 20080823180546
  • MySQL's internal timestamp format: 2008-08-23 18:05:46
  • UNIX timestamp format 1219514746 (número de segundos desde el 1 de enero de 1970)

In the output, timestamps are always in ISO 8601 format.


MediaWiki API has historically supported a number of different formats, but this has significantly complicated further development. We would like to standardize on just one JSON format. For now, MediaWiki discourages, but still supports two additional generic output formats (XML and PHP). You should always specify the format with the input (request) parameter format and a lowercase value. Feed modules like Feed Recent Changes override the standard output format, instead using RSS or Atom, as specified by their feedformat parameter. In those cases, the format specified in the format parameter is only used if there's an error. All formats other than JSON are deprecated. XML and PHP are still supported, but all others have been removed in either MediaWiki 1.26 or 1.27; see the table below. All new API users should use JSON. Clients written in PHP should avoid using the PHP format because it is fundamentally insecure. It is maintained for now only due to its popularity.

Unless specified, all modules allow data output in all generic formats. To simplify debugging, all generic formats have "pretty-print in HTML" alternatives with an fm suffix.

The default format changed in MediaWiki 1.25 to jsonfm; it was xmlfm in earlier MediaWiki releases.

Note that while the pretty-print formats are all indented and separate syntactic elements with newlines, the non-pretty formats don't do this.

Formato Descripción
json Formato JSON (siempre usa este)
none Always return a blank response 1.21+
Desaconsejado, pero aún operacional
php Formato PHP serializado
xml Formato XML
Formatos eliminados en MediaWiki 1.26
wddx Formato WDDX
dump Formato PHP var_dump()
Formatos eliminados en MediaWiki 1.27
txt Formato PHP print_r()
dbg Formato PHP var_export()
yaml Formato YAML

There are many conversion libraries and online converters to convert JSON responses to other formats—for example, JSON-CSV converts to Comma-Separated Values

JSON parameters

format=json and jsonfm accept the following additional parameters:

  • callback: If specified, wraps the output into a given function call. For safety, all user-specific data will be restricted.
  • utf8: If specified, encodes most (but not all) non-ASCII characters as UTF-8 instead of replacing them with hexadecimal escape sequences.
  • formatversion Specify formatversion=2 for to get json (and php) format responses in a cleaner format. This also encodes most non-ASCII characters as UTF-8. MW 1.25+

Restricciones de devolución de llamada

When using JSON in callback mode, a number of things are disabled for security:

  • Tokens cannot be obtained (so state-changing actions aren't possible)
  • The client is treated as an anonymous user (i.e. not logged in) for all purposes, even after logging in through action=login
    • This means that things that require additional rights, such as rcprop=patrolled, won't work unless anonymous users are allowed to use them



it may be useful to add the '&indexpageids' parameter, to parse the json if the pageid ("736") is not known before the result.

JSON utf8 content on a French page, remove the utf8= parameter to see the difference


PHP (serialized format, with line breaks added for readability. Use PHP's unserialize() function to recover data.)

PHP (var_export format)