API:編集
 | このページは MediaWiki 操作 API の説明文書の一部です。 |
| MediaWiki バージョン: | ≧ 1.13 |
ページを編集する POST リクエストです。
APIの説明文書
例
この例のサンプルコードはPythonです。 See API:Edit/Editing with Ajax for examples and responses in Ajax.
POST リクエスト
Making edits, and, indeed, any POST request, is a multi-step process.
- 1. Log in, via one of the methods described in API:ログイン. Note that while this is required to correctly attribute the edit to its author, many wikis do allow users to edit without registering or logging into an account.
- 2. GET a CSRF token:
- 3. Send a POST request, with the CSRF token, to take action on a page:
The Response section below is for the final POST request, to take action on the page. See the pages on API:ログイン and API:トークン for the intermediary JSON responses to earlier steps.
Also note that the tokens in the queries on this page are sample values. Actual tokens are unique to each login session and cross-site request. They are included only to demonstrate how to properly format queries.
レスポンス
{
"edit": {
"result": "Success",
"pageid": 94542,
"title": "Wikipedia:Sandbox",
"contentmodel": "wikitext",
"oldrevid": 371705,
"newrevid": 371707,
"newtimestamp": "2018-12-18T16:59:42Z"
}
}
サンプル コード
Python
#!/usr/bin/python3
"""
edit.py
MediaWiki API Demos
Demo of `Edit` module: POST request to edit a page
MIT license
"""
import requests
S = requests.Session()
URL = "https://test.wikipedia.org/w/api.php"
# Step 1: GET request to fetch login token
PARAMS_0 = {
"action": "query",
"meta": "tokens",
"type": "login",
"format": "json"
}
R = S.get(url=URL, params=PARAMS_0)
DATA = R.json()
LOGIN_TOKEN = DATA['query']['tokens']['logintoken']
# Step 2: POST request to log in. Use of main account for login is not
# supported. Obtain credentials via Special:BotPasswords
# (https://www.mediawiki.org/wiki/Special:BotPasswords) for lgname & lgpassword
PARAMS_1 = {
"action": "login",
"lgname": "bot_user_name",
"lgpassword": "bot_password",
"lgtoken": LOGIN_TOKEN,
"format": "json"
}
R = S.post(URL, data=PARAMS_1)
# Step 3: GET request to fetch CSRF token
PARAMS_2 = {
"action": "query",
"meta": "tokens",
"format": "json"
}
R = S.get(url=URL, params=PARAMS_2)
DATA = R.json()
CSRF_TOKEN = DATA['query']['tokens']['csrftoken']
# Step 4: POST request to edit a page
PARAMS_3 = {
"action": "edit",
"title": "Project:Sandbox",
"token": CSRF_TOKEN,
"format": "json",
"appendtext": "Hello"
}
R = S.post(URL, data=PARAMS_3)
DATA = R.json()
print(DATA)
PHP
<?php
/*
edit.php
MediaWiki API Demos
Demo of `Edit` module: POST request to edit a page
MIT license
*/
$endPoint = "https://test.wikipedia.org/w/api.php";
$login_Token = getLoginToken(); // Step 1
loginRequest( $login_Token ); // Step 2
$csrf_Token = getCSRFToken(); // Step 3
editRequest($csrf_Token); // Step 4
// Step 1: GET request to fetch login token
function getLoginToken() {
global $endPoint;
$params1 = [
"action" => "query",
"meta" => "tokens",
"type" => "login",
"format" => "json"
];
$url = $endPoint . "?" . http_build_query( $params1 );
$ch = curl_init( $url );
curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true );
curl_setopt( $ch, CURLOPT_COOKIEJAR, "cookie.txt" );
curl_setopt( $ch, CURLOPT_COOKIEFILE, "cookie.txt" );
$output = curl_exec( $ch );
curl_close( $ch );
$result = json_decode( $output, true );
return $result["query"]["tokens"]["logintoken"];
}
// Step 2: POST request to log in. Use of main account for login is not
// supported. Obtain credentials via Special:BotPasswords
// (https://www.mediawiki.org/wiki/Special:BotPasswords) for lgname & lgpassword
function loginRequest( $logintoken ) {
global $endPoint;
$params2 = [
"action" => "login",
"lgname" => "bot_user_name",
"lgpassword" => "bot_password",
"lgtoken" => $logintoken,
"format" => "json"
];
$ch = curl_init();
curl_setopt( $ch, CURLOPT_URL, $endPoint );
curl_setopt( $ch, CURLOPT_POST, true );
curl_setopt( $ch, CURLOPT_POSTFIELDS, http_build_query( $params2 ) );
curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true );
curl_setopt( $ch, CURLOPT_COOKIEJAR, "cookie.txt" );
curl_setopt( $ch, CURLOPT_COOKIEFILE, "cookie.txt" );
$output = curl_exec( $ch );
curl_close( $ch );
}
// Step 3: GET request to fetch CSRF token
function getCSRFToken() {
global $endPoint;
$params3 = [
"action" => "query",
"meta" => "tokens",
"format" => "json"
];
$url = $endPoint . "?" . http_build_query( $params3 );
$ch = curl_init( $url );
curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true );
curl_setopt( $ch, CURLOPT_COOKIEJAR, "cookie.txt" );
curl_setopt( $ch, CURLOPT_COOKIEFILE, "cookie.txt" );
$output = curl_exec( $ch );
curl_close( $ch );
$result = json_decode( $output, true );
return $result["query"]["tokens"]["csrftoken"];
}
// Step 4: POST request to edit a page
function editRequest( $csrftoken ) {
global $endPoint;
$params4 = [
"action" => "edit",
"title" => "Project:Sandbox",
"appendtext" => "Hello",
"token" => $csrftoken,
"format" => "json"
];
$ch = curl_init();
curl_setopt( $ch, CURLOPT_URL, $endPoint );
curl_setopt( $ch, CURLOPT_POST, true );
curl_setopt( $ch, CURLOPT_POSTFIELDS, http_build_query( $params4 ) );
curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true );
curl_setopt( $ch, CURLOPT_COOKIEJAR, "cookie.txt" );
curl_setopt( $ch, CURLOPT_COOKIEFILE, "cookie.txt" );
$output = curl_exec( $ch );
curl_close( $ch );
echo ( $output );
}
JavaScript
/*
edit.js
MediaWiki API Demos
Demo of `Edit` module: POST request to edit a page
MIT license
*/
var request = require('request').defaults({jar: true}),
url = "https://test.wikipedia.org/w/api.php";
// Step 1: GET request to fetch login token
function getLoginToken() {
var params_0 = {
action: "query",
meta: "tokens",
type: "login",
format: "json"
};
request.get({ url: url, qs: params_0 }, function (error, res, body) {
if (error) {
return;
}
var data = JSON.parse(body);
loginRequest(data.query.tokens.logintoken);
});
}
// Step 2: POST request to log in.
// Use of main account for login is not
// supported. Obtain credentials via Special:BotPasswords
// (https://www.mediawiki.org/wiki/Special:BotPasswords) for lgname & lgpassword
function loginRequest(login_token) {
var params_1 = {
action: "login",
lgname: "bot_username",
lgpassword: "bot_password",
lgtoken: login_token,
format: "json"
};
request.post({ url: url, form: params_1 }, function (error, res, body) {
if (error) {
return;
}
getCsrfToken();
});
}
// Step 3: GET request to fetch CSRF token
function getCsrfToken() {
var params_2 = {
action: "query",
meta: "tokens",
format: "json"
};
request.get({ url: url, qs: params_2 }, function(error, res, body) {
if (error) {
return;
}
var data = JSON.parse(body);
editRequest(data.query.tokens.csrftoken);
});
}
// Step 4: POST request to edit a page
function editRequest(csrf_token) {
var params_3 = {
action: "edit",
title: "Project:Sandbox",
appendtext: "test edit",
token: csrf_token,
format: "json"
};
request.post({ url: url, form: params_3 }, function (error, res, body) {
if (error) {
return;
}
console.log(body);
});
}
// Start From Step 1
getLoginToken();
MediaWiki JS
/*
edit.js
MediaWiki API Demos
Demo of `Edit` module: POST request to edit a page
MIT License
*/
var params = {
action: 'edit',
title: 'Project:Sandbox',
appendtext: 'Hello',
format: 'json'
},
api = new mw.Api();
api.postWithToken( 'csrf', params ).done( function ( data ) {
console.log( data );
} );
User cases
編集の競合
The Python sample is a basic implementation of an edit request by a registered user. In real-world scenarios, care should be taken to prevent edit conflicts. These occur when two or more users are attempting to edit the same page at the same time.
Conflicts can be prevented by retrieving the last revision timestamp when we request a CSRF token.
Adding prop=info|revisions to the CSRF token request in Step 3 allows us to access the timestamp for the last revision.
This timestamp will be used as the basetimestamp when we make our the edit request.
We also need the exact time when we start our edit.
This can be retrieved by adding curtimestamp to the CSRF request as well.
This value will serve as our starttimestamp.
Finally, in the actual edit request, set the basetimestamp and starttimestamp parameters, like so:
Large edits
POST requests containing large amounts of text content (8000+ characters) should be sent with Content-Type: multipart/form-data indicated in the header.
Because multipart/form-data does not need to add HTML escape characters (i.e., percent encoding) for spaces and punctuation, the amount of data passed will subsequently be much smaller than the percent-encoded equivalent.
However, there is still some overhead added by multipart/form-data -- roughly, 160 bytes per parameter.
For short messages that don't require adding many escape characters, this amount of overhead can be inefficient, and percent-encoding is preferred.[1]
Note that in our Python sample code, the request is percent-encoded by default.
See the MDN web docs for a more technical discussion of content-type and POST requests.
See the Python Requests documentation for how to pass multipart/form-data using syntax similar to our Python sample code.
CAPTCHA
If the wiki you are targeting uses CAPTCHAs, your request may return an error containing an ID number and a simple test, such as a question, a math problem, or an URL to an image.
In order to complete your edit, you must complete the test, then retry your request with the id and the correct answer(s) appended to the original query string, like so: captchaid=sampleId&captchaword=answer
Other CAPTCHA systems and extensions may use different parameters for similar use. In general, use the field names for the ID and test questions as the parameters in your second request.
起こりうるエラー
| コード | 情報 |
|---|---|
| notitle | パラメーター title を設定してください。 |
| missingparam | At least one of the parameters text、appendtext および undo is required. |
| notoken | パラメーター token を設定してください。 |
| invalidsection | The section parameter must be a valid section ID or new. |
| protectedpage | このページは編集や他の操作ができないように保護されています。 |
| cantcreate | 新しいページを作成する権限がありません。 |
| cantcreate-anon | Anonymous users can't create new pages |
| articleexists | The page you tried to create has been created already. |
| noimageredirect-anon | Anonymous users can't create image redirects. |
| noimageredirect | 画像のリダイレクトを作成する権限がありません。 |
| spamdetected | Your edit was refused because it contained a spam fragment: Wikitext.
|
| abusefilter-warning | This action has been automatically identified as harmful. |
| abusefilter-disallowed | This action has been automatically identified as harmful, and therefore disallowed. |
| contenttoobig | The content you supplied exceeds the page size limit of bytes kibibytes. Where bytes is the value of $wgMaxArticleSize. |
| noedit-anon | Anonymous users can't edit pages. |
| noedit | あなたにはページを編集する権限がありません。 |
| pagedeleted | The page has been deleted since you fetched its timestamp. |
| emptypage | 内容がないページの新規作成は許可されていません。 |
| emptynewsection | Creating empty new sections is not possible. |
| editconflict | 編集が競合。 |
| revwrongpage | 版 revid は pagename の版ではありません。 Thrown if an invalid revid is given for undo or undoafter
|
| undofailure | 中間の版での編集と競合したため、取り消せませんでした。 |
| missingtitle | The page you specified doesn't exist. (see above nocreate parameter)
|
| mustbeposted | The edit module requires a POST request. |
| readapidenied | このモジュールを使用するにはページを閲覧する権限が必要です。 |
| writeapidenied | You're not allowed to edit this wiki through the API. |
| noapiwrite | Editing of this wiki through the API is disabled. |
| badtoken | Invalid CSRF token. |
| missingparam | パラメーター title, pageid を設定してください。 |
| invalidparammix | The parameters title, pageid can not be used together. |
| invalidtitle | Bad title "title". |
| invalid-content-data | 本文データが無効です occurs when trying to edit a JSON page with non-conforming data, or while trying to edit a MassMessageListContent page |
| nosuchpageid | ID pageid のページはありません。 |
| pagecannotexist | Namespace doesn't allow actual pages. |
| nosuchrevid | There is no revision with ID undo. |
| nosuchrevid | There is no revision with ID undoafter. |
| badmd5 | The supplied MD5 hash was incorrect. |
| hookaborted | 拡張機能のフックによって、修正が中断されました。 |
| parseerror | Content serialization failed: parseerror |
| summaryrequired | ⧼apierror-summaryrequired⧽ |
| blocked | You have been blocked from editing. |
| ratelimited | You've exceeded your rate limit. Please wait some time and try again. |
| unknownerror | 不明なエラー:「retval」 |
| nosuchsection | There is no section $1. |
| sectionsnotsupported | Sections are not supported for content model $1. |
| editnotsupported | Editing of this type of page is not supported using the text based edit API. |
| appendnotsupported | Can't append to pages using content model $1. |
| redirect-appendonly | You have attempted to edit using the redirect-following mode, which must be used in conjunction with section=new, prependtext, or appendtext. |
| edit-invalidredirect | Cannot edit $1 while following redirects, as target $2 is not valid. |
| badformat | The requested format $1 is not supported for content model $2 used by $3. |
| customcssprotected | この CSS ページは他の利用者の個人設定を含んでいるため、あなたには編集する権限がありません。 |
| customjsprotected | この JavaScript ページは他の利用者の個人設定を含んでいるため、あなたには編集する権限がありません。 |
| taggingnotallowed | You don't have permission to set change tags |
| badtags | タグ "Tag" の手動適用は認められていません。 以下の タグ は手動適用が認められていません: Tag1、 Tag2 |
| tpt-target-page | このページは手動では更新できません。
このページはページ $1 の翻訳版であり、[$2 翻訳ツール]を使用して更新できます。 |
パラメーターの履歴
- v1.35:
baserevidを導入しました - v1.25:
tagsを導入しました - v1.21:
contentformat,contentmodelを導入しました - v1.20:
pageidを導入しました - v1.19:
sectiontitleを導入しました - v1.18:
captchaid,captchawordを廃止予定にしました - v1.17:
redirectを導入しました - v1.16:
watch,unwatchを廃止予定にしました - v1.16:
watchlistを導入しました - v1.15:
undo,undoafterを導入しました - v1.14:
starttimestampを導入しました
追加的な注記
- Log in is not strictly required by the API, but it is needed to correctly attribute the edit to its author.
A successful edit from a user who is not logged in will be attributed to their IP address.
- Bots that are not logged in may face restrictions on editing and other write requests; see Manual:Creating a bot#Logging in for more details.
- Users who are not logged in will always be given the empty CSRF token,
+\.
- The process for requesting a token has changed several times across versions.
詳細情報は API:トークン を参照してください。
- ResourceLoader provides a way to access edit tokens when running code within a wiki page.
- You can use the same CSRF token for all edit operations across the same wiki, during a single login session.
- It is a good practice to pass any tokens in your request at the end of the query string, or at least after the text parameter.
That way, if the connection is interrupted, the token will not be passed and the edit will fail. If you are using the mw.Api object to make requests, this is done automatically.
- Although
captchaidandcaptchawordhave, technically, been removed from API:Edit since v1.18, Extension:ConfirmEdit extends API:Edit to work with CAPTCHAs.
Thus, with ConfirmEdit installed, these parameters are still available. ConfirmEdit comes packaged with the MediaWiki software, v1.18+.
関連項目
- Help:編集 - contains useful links on editing articles.
- Manual:ボットのパスワード - describes how to log in using a simplified interface when accessing wikis via a script or application, rather than the GUI.
- Manual:Creating a bot - more details on using a bot to automatically edit pages.
- ResourceLoader - provides a way to access edit tokens when running JavaScript within a MediaWiki page.
- API:トークン - has more details on using tokens to log in or make POST requests.
- API:tokens (操作) - a deprecated API, distinct from API:トークン, for requesting tokens in earlier versions of MediaWiki.
- API:比較 - allows you to diff between edits on a page.
- API:タグ管理 - alters tags on a page.
- API:巻き戻し - reverts a series of edits.
- API:ファイルの差し戻し - rolls back files to an earlier state.
- API:版指定削除 - deletes and restores revisions to a page.