Wikipedia Pageviews API

The Wikipedia Pageviews API is part of the Wikimedia Analytics (AQS) REST API. It exposes historical pageview, edit, and editor metrics for articles and projects across Wikimedia wikis, letting you pull daily and monthly counts for any article, project, or region. It is a public API that requires no account or key, though Wikimedia asks that every client identify itself with a descriptive User-Agent header.

Power end-to-end data operations for your Wikipedia Pageviews API API with Nexla. Our bi-directional Wikipedia Pageviews API connector is purpose-built for Wikipedia Pageviews API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Wikipedia Pageviews API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Wikipedia Pageviews API workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The Wikimedia Analytics API is open and does not require an API key, token, or sign-in — all endpoints under the metrics namespace are publicly readable. To configure this connector in Nexla, you only need the API base URL, which defaults to https://wikimedia.org/api/rest_v1.

Keep the following in mind when using the API:

1. Identify your client. Wikimedia asks that every client send a meaningful User-Agent header that includes contact information (an email address or project URL) so that operators can reach you if a request pattern causes problems.

2. Respect the request rate. There is no fixed request quota, but clients that endanger service stability may be throttled or blocked. As a safe practice, wait for each request to finish before issuing the next one.

3. Review the access policy. Some metrics are subject to data-retention and privacy rules. Confirm your intended use against the Wikimedia access policy before building production flows.

For full endpoint details, path parameters, and response formats, see the Wikimedia Analytics API documentation and the access policy.

Authenticate

Credentials required

Field	Required	Secret	Description
Base URL	Yes	No	The base URL for the Wikipedia Pageviews API. Defaults to https://wikimedia.org/api/rest_v1.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter the API base URL in the Base URL field, or leave the default value https://wikimedia.org/api/rest_v1 in place. This value is combined with the endpoint path to construct each request URL.

   The Wikipedia Pageviews API requires no authentication — the Base URL is the only field needed to connect. Wikimedia does, however, ask that clients send a descriptive User-Agent header with contact information; see the Wikimedia API rate limits guidance for details.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Wikipedia Pageviews API connector tile, then select the credential that will be used to connect, and click Next; or, create a new Wikipedia Pageviews API credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Wikipedia Pageviews API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] Get Article Pageviews

Returns daily pageview statistics for a specific article on Wikipedia.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get Top Pageviews

Returns the most viewed articles on Wikipedia for a specified time period.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get top 100 edited pages by absolute bytes difference

Returns the top 100 pages ranked by absolute bytes difference for a specific project, editor type, and page type on a given date.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get top 100 edited pages by edits count

Returns the top 100 pages ranked by number of edits for a specific project, editor type, and page type on a given date.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get top 100 edited pages by net bytes difference

Returns the top 100 pages ranked by net bytes difference for a specific project, editor type, and page type on a given date.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get editors counts for a project

Returns aggregated editor counts for a project within a specified date range and granularity, filtered by editor type, page type, and activity level.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get top 100 editors by absolute bytes difference

Returns the top 100 editors ranked by absolute bytes difference for a specific project, editor type, and page type on a given date.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get top 100 editors by edits count

Returns the top 100 editors ranked by number of edits for a specific project, editor type, and page type on a given date.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get top 100 editors by net bytes difference

Returns the top 100 editors ranked by net bytes difference for a specific project, editor type, and page type on a given date.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get edits counts for a project

Returns aggregated edit counts for a project within a specified date range and granularity, filtered by editor type and page type.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get edit counts for a page

Returns edit counts for a specific page in a project within a specified date range and granularity, filtered by editor type.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get legacy pagecounts aggregate

Returns aggregated legacy pagecount metrics for a project within a specified date range and granularity, filtered by access type and site.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get pageview counts for a project

Returns aggregated pageview counts for a project across specified time period, access type, and agent type.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get pageview counts for a page

Returns pageview counts for a specific article across a specified time period, access type, and agent type.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get pageviews by country and access method

Returns the top countries by pageview volume for a project during a specified month and access method.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get the most viewed articles for a project

Returns the most viewed articles for a project during a specified day and access method.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get newly registered users counts for a project

Returns the count of newly registered users for a project across a specified time period and granularity.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get Word Dictionary Translation

Fetch the dictionary meaning and translation of a word between two languages

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Get Word Dictionary Translation from Provider

Fetch the dictionary meaning and translation of a word between two languages from a specific provider

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Wikipedia Pageviews API data sources can also be manually configured to ingest data from any valid Wikimedia Analytics API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Wikipedia Pageviews API data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Wikipedia Pageviews API destination, and select the Send to Destination option from the menu. Select the Wikipedia Pageviews API connector from the list of available destination connectors, then select the credential that will be used to connect, and click Next; or, create a new Wikipedia Pageviews API credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to Wikipedia Pageviews API endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Check Math Formula

Checks and normalizes a TeX formula by type.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Machine-translate content

Translates HTML content from one language to another using machine translation.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

[Rest API] Translate HTML with provider

Translates HTML content from one language to another using a specified machine translation provider.

For the full list of path parameters, response fields, and usage notes for this endpoint, see the Wikimedia Analytics API documentation.

Manual configuration

Wikipedia Pageviews API destinations can also be manually configured to send data to any valid Wikimedia REST API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Wikipedia Pageviews API endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Wikipedia Pageviews API endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.