[[[{GraficImagesStatics2.3}]]] [[[{Holograms6GPics2.3}]]] [[[{GrapgeoPc2.3.3}]]] [[[{SacetySafeData2.4}]]] [[{MestLine2.5}]] [[{datawiki2.5.5}]
User talk:Putrakedah
This page is part of the MediaWiki action API documentation. |
MediaWiki action API
- Introduction and quick start
- FAQ
- Tutorial
- Formats
- Error reporting
- Restricting usage
- Cross-site requests
- Authentication
- Queries
- Searching (by title, content, coordinates...)
- Parsing wikitext and expanding templates
- Purging pages' caches
- Parameter information
- Changing wiki content
- Create and edit pages
- Move pages
- Merge pages
- Rollback
- Delete pages
- Restore deleted revisions
- (Un)protect pages
- (Un)block users
- (Un)watch pages
- Mark revisions of watched pages as visited
- Send email
- Patrol changes
- Import pages
- Change user group membership
- Upload files
- User options
- Tokens
- Page language
- Watchlist feed
- Wikidata
- Extensions
- Using the API in MediaWiki and extensions
- Miscellaneous
- Implementation
- Client code
- Asserting
The MediaWiki API may require your application or client to provide authenticated user credentials to the API in order to complete an operation successfully. As of MediaWiki 1.27, there are two API actions used to authenticate: login
and clientlogin
.
<translate>
Bots and other non-interactive applications should generally use [[<tvar|oauthowneronly>Special:MyLanguage/OAuth/Owner-only consumers</>|owner-only OAuth consumers]] when available to authenticate as it is more secure, however [[<tvar|botpasswords>Special:MyLanguage/Manual:Bot passwords</>|bot passwords]] can be used with the login
action as described on this page.
Interactive applications such as custom editors or patrolling applications that provide a service without intending to fully replace the website should generally also use [[<tvar|oauthfordevelopers>Special:MyLanguage/OAuth/For Developers</>|OAuth]] for authenticating the tool, as it is easier and more secure, however the clientlogin
action can be used if that is unavailable.
Interactive applications such as mobile apps that aim to completely replace access to the web-based user interface should use the clientlogin
action to authenticate.