From MediaWiki.org
Jump to: navigation, search
Language: English  • Deutsch • 日本語
Tools clipart.png This page is part of the MediaWiki action API documentation.
MediaWiki APIsAPI:Main page

MediaWiki action API

v · d · e
MediaWiki version: 1.12


To change a page's protection level, a CSRF token is required. This token is the same for all pages, but changes at every login. CSRF tokens can be obtained via action=query&meta=tokens with type=csrf (MW 1.24+).

In previous versions of MediaWiki, a protect token was required (deprecated) This token is equal to the edit token and the same for all pages, but changes at every login. Protect tokens can be obtained via action=tokens with type=protect (MW 1.20+), or by using the following method:

Obtaining a protect token (deprecated)

Protecting pages[edit]

Pages can be protected with action=protect.


  • title: The page you want to protect.
  • token: The token obtained in the previous request. Take care to urlencode the + as %2B.
  • protections: A pipe-separated list of protections, formatted as action=group, e.g. edit=autoconfirmed|move=sysop
    • If you want to remove a protection, use all as group, e.g. edit=all|move=sysop
    • If you leave out an action, the associated value won't be changed, i.e. edit=sysop leaves the move protection untouched.
  • expiry: Pipe-separated list of expiry timestamps in GNU timestamp format. The first timestamp applies to the first protection in protections, the second to the second, etc. The timestamps infinite, indefinite and never result in a protection that will never expire. Timestamps like next Monday 16:04:57 or 9:28 PM tomorrow are also allowed, see the GNU web site for details.
    • The number of expiry timestamps must equal the number of protections, or you'll get an error message
      • An exception to this rule is made for backwards compatibility: if you specify exactly one expiry timestamp, it'll apply to all protections
    • Not setting this parameter is equivalent to setting it to infinite
  • reason: The reason for the (un)protection (optional).
  • cascade: If set, pages transcluded in the protected page will also be protected. If the required user level to edit is lower than the required user level to protect (e.g. edit=autoconfirmed), cascading can't be enabled, and this parameter will be silently ignored.
    • The latter is to prevent people who shouldn't be able to protect pages from protecting them anyway by transcluding them in a page with cascading protection.


Note: In this example, all parameters are passed in a GET request just for the sake of simplicity. However, action=protect requires POST requests; GET requests will cause an error.

Protecting the Main Page edit=autoconfirmed, move=sysop, the first expiring February 24, 2015 at 12:34:56, the second expiring March 25, 2015 at 13:06:20 with cascading protection enabled.

Protecting "Deletion log" create=sysop, expiring a 2 months from now

Possible errors[edit]

In addition to the usual stuff:

Code Info
notitle The title parameter must be set
notoken The token parameter must be set
noprotections The protections parameter must be set
invalidexpiry Invalid expiry time "expiry"
Note: This means the expiry timestamp was invalidly formatted, or is nonexistent (like November 31 or 24:05).
pastexpiry Expiry time "expiry" is in the past
toofewexpiries number expiry timestamps were provided where number were needed
Note: This error is misnamed: it's also thrown when you specify too many expiry times
cantedit You can't protect this page because you can't edit it
create-titleexists Existing titles can't be protected with 'create'
missingtitle-createonly Missing titles can only be protected with 'create'
protect-invalidaction Invalid protection type "type"
protect-invalidlevel Invalid protection level "level"