How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Wikipedia / MediaWiki Page content API

page content in different formats

Wikipedia / MediaWiki Page content API is one of 28 APIs that Wikipedia / MediaWiki publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Page content. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and pricing.

This API exposes 14 operations across 14 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://en.wikipedia.org/api/rest_v1, https://{lang}.wikipedia.org/api/rest_v1.

14 operations 14 paths 10 schemas 14 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://en.wikipedia.org/w/api.php
License
Terms of Service
Resource Areas
1

Paths & Operations 14

Across 14 paths, the API surfaces 14 operations — 14 GET. Each is listed below with its method, path, parameters, and response codes.

Page Content 14

page content in different formats

GET
/page/
Wikimedia REST List Page-related API Entry Points
getPage → 200default
GET
/page/title/{title}
Wikimedia REST Get Revision Metadata for a Title
getPageTitleByTitle 1 param → 200301302404default
GET
/page/title/{title}/{revision}
Wikimedia REST Get Revision Metadata for a Title
getPageTitleByTitleByRevision 2 params → 200301302404default
GET
/page/html/{title}
Wikimedia REST Get Latest HTML for a Title
getPageHtmlByTitle 4 params → 200301302404default
GET
/page/html/{title}/{revision}
Wikimedia REST Get HTML for a Specific Title/revision & Optionally Timeuuid
getFormatRevision 5 params → 200301302400403404default
GET
/page/lint/{title}
Wikimedia REST Get the Linter Errors for a Specific Title/revision
getPageLintByTitle 1 param → 200301302400403404default
GET
/page/lint/{title}/{revision}
Wikimedia REST Get the Linter Errors for a Specific Title/revision
getPageLintByTitleByRevision 2 params → 200301302400403404default
GET
/page/summary/{title}
Wikimedia REST Get Basic Metadata and Simplified Article Introduction
getPageSummaryByTitle 3 params → 200301302404default
GET
/page/media-list/{title}
Wikimedia REST Get List of Media Files Used on a Page
getContent-media-list 2 params → 200301302404default
GET
/page/media-list/{title}/{revision}
Wikimedia REST Get List of Media Files Used on a Page
getContentWithRevision-media-list 3 params → 200301302404default
GET
/page/mobile-html/{title}
Wikimedia REST Get Page Content HTML Optimized for Mobile Consumption
getContent-mobile-html 2 params → 200301302404default
GET
/page/mobile-html/{title}/{revision}
Wikimedia REST Get Page Content HTML Optimized for Mobile Consumption
getContentWithRevision-mobile-html 3 params → 200301302404default
GET
/page/mobile-html-offline-resources/{title}
Wikimedia REST Get Styles and Scripts for Offline Consumption of…
getPageMobileHtmlOfflineResourcesByTitle 1 param → 200default
GET
/page/mobile-html-offline-resources/{title}/{revision}
Wikimedia REST Get Styles and Scripts for Offline Consumption of…
getPageMobileHtmlOfflineResourcesByTitleByRevision 2 params → 200default

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are summary (13 properties), revisionInfo (12 properties), media_item (6 properties), problem (4 properties). Each schema is shown below with its type and property counts.

problem
object
4 properties 1 required
media_item
object
6 properties 3 required
originalimage
object
3 properties 3 required
listing
object
The result format for listings
2 properties 1 required
media_list
object
3 properties 3 required
revisionInfo
object
Complete information about the revision
12 properties
revision
object
Result format for revision items
2 properties 2 required
thumbnail
object
3 properties 3 required
summary
object
13 properties 4 required
titles_set
object
a good example of the differences can be seen in https://en.wikipedia.org/api/restv1/page/summary/IOS13
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wikipedia-page-content-api-openapi.yml Raw ↑

Other APIs Wikipedia / MediaWiki publishes across the network.

Wikipedia / MediaWiki articles API
Wikipedia / MediaWiki batches API
Wikipedia / MediaWiki Citation API
Wikipedia / MediaWiki Codes API
Wikipedia / MediaWiki Languages API
Wikipedia / MediaWiki Math API
Wikipedia / MediaWiki Mobile API
Wikipedia / MediaWiki Namespaces API
Wikipedia / MediaWiki Offline API
Wikipedia / MediaWiki Projects API
Wikipedia / MediaWiki Reading lists API
Wikipedia / MediaWiki Recommendation API
Where this information came from

This is an independent, third-party profile of Wikipedia / MediaWiki Page content API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.