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

Wikivoyage History API

Travel article revision history and edit statistics

Wikivoyage History API is one of 9 APIs that Wikivoyage publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include History. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against 3 base URLs: https://en.wikivoyage.org/w/rest.php/v1, https://{lang}.wikivoyage.org/w/rest.php/v1, https://api.wikimedia.org/core/v1/wikivoyage/{lang}.

2 operations 2 paths 4 schemas 2 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.wikivoyage.org/w/api.php
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Wikivoyage History API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth).

  • BearerAuth — OAuth 2.0 bearer token issued via api.wikimedia.org. Required for write operations on Wikivoyage travel articles.

Paths & Operations 2

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

History 2

Travel article revision history and edit statistics

GET
/page/{title}/history
Wikivoyage Core REST Get Travel Article Revision History
getPageHistory 4 params → 200404
GET
/page/{title}/history/counts/{type}
Wikivoyage Core REST Get Edit Statistics for a Travel Article
getPageHistoryCounts 2 params → 200404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Revision (10 properties), HistoryResponse (4 properties), EditCounts (2 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
HistoryResponse
object
4 properties
EditCounts
object
2 properties
Revision
object
A travel article revision.
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wikivoyage-history-api-openapi.yml Raw ↑

Other APIs Wikivoyage publishes across the network.

Wikivoyage Edit API
Wikivoyage Files API
Wikivoyage Links API
Wikivoyage Pages API
Wikivoyage Query API
Wikivoyage Revisions API
Wikivoyage Search API
Wikivoyage Transforms API
Where this information came from

This is an independent, third-party profile of Wikivoyage History 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.