Social Fetch
Start for freeStart free
Wikipedia hub

Wikipedia Recent Changes API

Live edits and log events, filtered by type, namespace, page or time.

GET /v1/wikipedia/recent-changes

1 credit Failed requests are free

Try in playgroundFull API docs

About this endpoint

GET /v1/wikipedia/recent-changes?lang=en returns data.changes, one row per change. Each row has type, ns, title, pageId, revId, oldRevId, rcid, user, userId, bot, new, minor, temp, oldLength, newLength, timestamp, comment, redirect, tags and sha1. Log rows add logId, logType, logAction and logParams. temp marks an automatically named temporary account.

type narrows to edit, new, log, categorize or external. namespace narrows to one namespace, title to one page, and since returns changes at or after an ISO 8601 time. limit accepts 1 to 500 rows and cursor continues with data.page.nextCursor.

This is a changing feed. A page of results is a snapshot of the window, and a later request can contain new rows. A filter that matches nothing is found with empty: true.

Wikipedia Recent Changes API FAQ

Can I follow one page's changes?

Pass title with the page title and read changes for that page. Combine it with since to get changes after the last time you checked.

What do the change types mean?

edit is an edit to an existing page, new is a page creation, log is a public log event, categorize is a category membership change, and external is an external link change.

Why can rows repeat between requests?

Recent changes is a live feed. A later request can include a change you already saw if the window overlaps. Use rcid or revId to de-duplicate your side.

How is recent-change paging billed?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth. Each paginated page is a separate billed request.

Other Wikipedia endpoints