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

Wikimedia structured-snapshots API

(BETA) Structured Contents Snapshot API

Wikimedia structured-snapshots API is one of 20 APIs that Wikimedia publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include structured-snapshots. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, rate-limit docs, and pricing.

This API exposes 6 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.enterprise.wikimedia.com.

6 operations 3 paths 7 schemas 3 GET1 HEAD2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://en.wikipedia.org/w/api.php
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Wikimedia structured-snapshots API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 6

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

structured-snapshots 6

(BETA) Structured Contents Snapshot API

GET
/v2/snapshots/structured-contents
2 params → 200401403422500
POST
/v2/snapshots/structured-contents
body → 200401403422500
GET
/v2/snapshots/structured-contents/{identifier}
2 params → 200401403404422500
POST
/v2/snapshots/structured-contents/{identifier}
1 param body → 200401403404422500
HEAD
/v2/snapshots/structured-contents/{identifier}/download
Project Structured Contents Snapshot Headers
1 param → 200401403404422500
GET
/v2/snapshots/structured-contents/{identifier}/download
2 params → 200401403404422500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are snapshot (8 properties), project (5 properties), language (4 properties), error (2 properties). Each schema is shown below with its type and property counts.

snapshot
object
8 properties
size
object
2 properties
article_namespace
object
1 property
filter
object
2 properties
error
object
2 properties
language
object
4 properties
project
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wikimedia-structured-snapshots-api-openapi.yml Raw ↑

Other APIs Wikimedia publishes across the network.

MediaWiki REST API
Wikimedia articles API
Wikimedia batches API
Wikimedia Citation API
Wikimedia codes API
Wikimedia languages API
Wikimedia Math API
Wikimedia Mobile API
Wikimedia namespaces API
Wikimedia offline API
Wikimedia Page content API
Wikimedia projects API
Where this information came from

This is an independent, third-party profile of Wikimedia structured-snapshots 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.