Wikipedia Page Revision State Evidence API

Monitor a known Wikipedia article watchlist without fetching article content. One Action API query for at most5 exact page IDs in one project, requesting only info and last-revision IDs/timestamp/size/SHA1. Existing rows must be namespace0. Supported projects: en,de,fr,es,it,tr. Missing or invalid-ID states are explicit billed observations with null revision/title fields; they do not prove deletion or say a title never existed. Existing redirects are reported as redirect pages without following them. Page identity is language plus numeric ID, so moves keep identity. Invalid/unexpected identities, namespaces, multiple revisions, continuation or API errors reject the source rather than invent state.

No article/wikitext, content diffs, images, editor usernames/IPs, edit comments, login, write action, user page, arbitrary wiki or whole-history crawl. Revision SHA1 and byte length are provider declarations, not digest verification or evidence that content is true. maxlag=5 is honored; lag/errors are not retried. touched is excluded from selected hashes because cache/indirect updates need not mean article changes. Use content attribution rules separately if you fetch the article downstream; this Actor does not fetch it. Cache/reduce calls and respect Wikimedia API policies.

Quick start

{"language": "en", "pageIds": [736, 147]}

Pricing and budget

0.0006 USD per emitted page state observation (0.6 USD per1000), plus0.005 USD startup at default256MB. Higher memory can multiply startup events; check effective Store pricing. Failed/empty sources do not emit result charges; startup can still apply. At zero result budget, input validation occurs but no upstream request is sent, and rowsAvailable is null (unknown). A positive budget can request the bounded source set before output; emission stops at the result cap and complete=false/PARTIAL_BUDGET reports truncation.

Snapshot, integration and limits

Use dataset rows together with OUTPUT and SNAPSHOT. Pass SNAPSHOT.previousHashes as previousHashes in a later run. NO_BASELINE/FIRST_SEEN/UNCHANGED/CHANGED compare only selected metadata including itemKey and sourceUrl; missing records are not deletions. FIRST_SEEN means absent from the supplied baseline. There is no persistent hidden state or automatic polling. Export JSON/CSV/Excel through the default dataset.

API example: POST https://api.apify.com/v2/actors/soilair~wikipedia-page-revision-state-evidence-api/runs with your Apify Authorization header and the JSON input above. Poll the returned run; read dataset items and OUTPUT/SNAPSHOT records using its store IDs. Do not place tokens or confidential data in input. No upstream key is needed. Results live in Apify run storage according to retention; no separate analytics service.

Only fixed HTTPS provider endpoints are constructed from validated identifiers. Public-IP DNS validation, pinned connections, TLS hostname verification,2MiB decoded responses, approximately95 seconds of network budget, at most5 same-provider redirects. Official API calls are distinct from website crawling; no arbitrary URLs or HTML pages. No linked documents/files are fetched. Queries are sequential with1-second spacing. Provider403/429 or Retry-After stops later calls; retry instructions are reported and no retry/proxy/circumvention is attempted. Shared IP limits and changes to upstream services can still block runs. Caller must respect provider headers and cache/reduce repeated requests. Text is data and should not be executed.

Developed with AI assistance. Tests and live/cloud comparisons qualify the selected-field contract; they do not prove commercial demand, provider uptime or a legal/license determination. Support: share a run ID and expected fields, without credentials or private material.

References: https://www.mediawiki.org/wiki/API:Revisions · https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_API_Usage_Guidelines/en