Talk:Community

Welcome to the discussion for the Community page! To leave a comment, log in and select Edit.

Feed api is down

When I try to fetch this api endpoint https://api.wikimedia.org/feed/v1/wikipedia/en/featured/2025/03/28 it gives me error like this:

{ "type": "https://mediawiki.org/wiki/HyperSwitch/errors/not_found#route", "title": "Not found.", "method": "get", "uri": "/en.wikipedia.org/v1/feed/featured/2025/03/28" } Alamin (talk) 07:35, 28 March 2025 (UTC)

Hi Alamin, Thanks for catching this! I was able to replicate the behavior you're seeing, have identified the issue, and have opened a bug report (phab:T390317). I expect we'll be able to get a fix out next week; I'll post again here to confirm once the fix is deployed. In the meantime, you can access the feed endpoints through the wiki URLs. For example: https://en.wikipedia.org/api/rest_v1/feed/featured/2025/03/28 --APaskulin (WMF) (talk) 20:55, 28 March 2025 (UTC)

This is now fixed! Let me know if you run into any other issues. APaskulin (WMF) (talk) 17:38, 2 April 2025 (UTC)

Well it works now but the news articles data is still missing in this api which was available before. Alamin (talk) 18:35, 17 April 2025 (UTC)

Hi, The news data is only available for the current day, not for any past days. For example, https://api.wikimedia.org/feed/v1/wikipedia/en/featured/2025/04/17 has the news data for today. APaskulin (WMF) (talk) 19:06, 17 April 2025 (UTC)

Feed API example is not visible

The endpoint example for curl, Python, PHP, JavaScript are not being shown. The title is there but the example endpoints are not visible. Actually, it shows up for a few milliseconds at the beginning of page load, but then it vanishes. Here is a screenshot of where the problem is: Screenshot link Alamin (talk) 09:47, 18 April 2025 (UTC)

Hi Alamin, Can you share the browser and the MediaWiki skin that you're using? --APaskulin (WMF) (talk) 16:17, 22 April 2025 (UTC)

I've updated the gadget, and the examples are visible for me now. Let me know if the examples still aren't working for you. APaskulin (WMF) (talk) 22:34, 2 July 2025 (UTC)

Announcement: API Portal shutdown

The Wikimedia Foundation has decided to shut down the API Portal wiki as part of a new strategy for Wikimedia APIs. We’re still working on exact plans and schedules, but here is a general idea of what to expect:

• Endpoints: api.wikimedia.org endpoints will continue to work as currently documented until at least June 2026. Starting in the second half of 2026, api.wikimedia.org endpoints will be migrated to new routes and eventually deprecated.
• API keys: Most API keys created through the API Portal will continue to work. You can manage your API keys through Special:OAuthConsumerRegistration on Meta-Wiki.
• Docs: Documentation from the API Portal will be consolidated and moved to other technical documentation wikis.

We’ll be providing more details about the planned shut down in the next couple of months. To get the latest updates, add this page to your watchlist or subscribe to the mediawiki-api-announce mailing list. We’d like to thank everyone who has contributed to the API Portal for being part of this community! We hope you'll continue to follow API projects in the future.

Background

In 2020, the Wikimedia Foundation Platform Engineering Team wanted to create a home for Wikimedia API docs that was similar to other popular API docs sites, and that allowed developers to more easily create and manage API keys.

Building the API Portal as a standalone wiki benefits from the advantages of MediaWiki:

• Ease of editing
• Ability to translate content
• Community collaboration through talk pages, watchlists, and other features

However, using a standalone wiki for the API Portal also has disadvantages:

• Administration: Each new wiki needs a community of administrators, page patrollers, and other functionaries. A new wiki adds work for the Wikimedia technical community.
• Technical complexity: MediaWiki is a complex ecosystem. Since the API Portal works differently from other Wikimedia wikis, we often find bugs that come from interactions with extensions, skins, and other wikis.
• Visual inconsistency: The API Portal’s simplified visual design makes it difficult to access wiki features like special pages. In addition, global skin preferences can override the API Portal’s visual design entirely, making the site difficult to use.

Wikimedia Foundation’s Product Management, MediaWiki Interfaces, and Tech Docs teams have decided that the disadvantages of implementing the API Portal as a standalone wiki outweigh the advantages. In 2026, we’ll be working on plans to overcome these disadvantages and reimagining ways to make API docs easy to find, use, and create. --APaskulin (WMF) (talk) 16:49, 22 January 2026 (UTC)

Hi all, Here's an update on the API Portal shut down:

• The API Portal wiki will be inaccessible starting in June 2026.
• To learn about Wikimedia APIs and find links to docs, visit the new landing page (work in progress) on mediawiki.org.
• Starting in late March or early April 2026, api.wikimedia.org endpoints will have the same rate limits as other Wikimedia APIs. The new rate limits are higher than the current rate limits, so this change should not create any issues. The Lift Wing API will continue to have the same custom rate limits with only minor clarifications.
• For a timeline and the latest project information, see the project page.

If you have any questions, want to share your feedback, or have any issues with functionality related to the API Portal, feel free to:

• Leave a comment here
• Post to the project talk page
• Email techdocs[at]wikimedia.org

APaskulin (WMF) (talk) 18:39, 18 March 2026 (UTC)

mostread missing from API result

Hi! I've been querying API daily since the start of 2026, specifically for the 'mostread' key in the result. But it seems like this has been missing since 2026/03/02 and onwards. The last available result that contains this key is for 2026/03/01. Did anything change here? Is this a result of the upcoming sunset of this API?

This is the endpoint i've been hitting: f"https://api.wikimedia.org/feed/v1/wikipedia/{lang}/featured/{y}/{m}/{d}"

Keys that were being returned on 2026/03/01 (and prior): dict_keys(['tfa', 'mostread', 'image', 'onthisday'])

Keys that are being returned on 2026/03/02 (and after): dict_keys(['tfa', 'image', 'onthisday']) -- 'mostread' is missing

Thanks! Cholo5ntrol (talk) 17:30, 3 March 2026 (UTC)

Hi @Cholo5ntrol, thanks for reporting this! mostread isn't available for the current date in UTC, but it should be available for 2026/03/02. I've opened a bug report here: phab:T418894. This shouldn't be related to the upcoming deprecation, but I'll comment back here when there's an update. APaskulin (WMF) (talk) 18:03, 3 March 2026 (UTC)

In the meantime, you can also call the Wikimedia Analytics API to list the most-viewed pages for a given day. APaskulin (WMF) (talk) 18:06, 3 March 2026 (UTC)

Hi @Cholo5ntrol, This endpoint seems to be working as expected now. Let me know if you have any further issues. APaskulin (WMF) (talk) 15:06, 4 March 2026 (UTC)

Thanks @APaskulin (WMF)! Confirming that it's working as expected now. Cholo5ntrol (talk) 15:33, 4 March 2026 (UTC)

I get an 500 internal server error whenever i try to call API with an API key

Since yesterday i get internal server error 500 whenever i try to call a wikipedia api with an valid api key: Example: https://de.wikipedia.org/w/api.php?action=query&list=geosearch&gsbbox=51.08363690226374%7C13.723847814149655%7C51.05171409773626%7C13.742289185850344&gslimit=500&maxlag=5&format=json&continue=

Without authentication it works. With token, it doesnt. Vibesolutions (talk) 11:04, 13 March 2026 (UTC)

Hi @Vibesolutions, Can you say more about which authentication flow you're using? It will help us troubleshoot your issue. APaskulin (WMF) (talk) 14:17, 13 March 2026 (UTC)

Hey @APaskulin (WMF). I use the app authentication flow.

The response is Internal Server Error 500. The response body is:

::<html>
::<head>
::<title>Interner Fehler – Wikipedia</title>
::<meta name="color-scheme" content="light dark" /><style>body { font-family: sans-serif; margin: 0; padding: 0.5em 2em; }</style>
::</head>
::<body>
::<div class="cdx-message--error cdx-message cdx-message--block"><span class="cdx-message__icon"></span>
::<div class="cdx-message__content">[634b3019-7662-4804-8bef-5c10b777d531] 2026-03-13 05:59:13: Fataler Ausnahmefehler des Typs „TypeError“</div>
::</div><!-- Set $wgShowExceptionDetails = true; at the bottom
:::of LocalSettings.php to show detailed debugging
:::information. --></body></html>
::

Here is how i retrieve the token:

::const clientId = this.getClientId();
::const clientSecret = this.getClientSecret();
::if (!clientId || !clientSecret) {
::   throw new Error("Wikimedia credentials are missing");
::}
::const body = new URLSearchParams({
::grant_type: "client_credentials",
::   client_id: clientId,
::   client_secret: clientSecret,
::});
::const response = await fetch("https://meta.wikimedia.org/w/rest.php/oauth2/access_token", {
:: method: "POST",
:: headers: {
::    "Content-Type": "application/x-www-form-urlencoded",
:: },
:: body: body.toString(),
::});
::if (response.ok) {
::const data = (await response.json()) as WikimediaTokenResponse;
::if (!data.access_token || !data.expires_in) {
::   throw new Error("Wikimedia token response is missing fields");
::}
::return data;
::}
::

the token retrieval works. But i can not call any api with that token. Vibesolutions (talk) 21:57, 13 March 2026 (UTC)

Hi @Vibesolutions, Thanks for sharing that info. My apologies that you are encountering this error. This is a known bug in our system. Here the bug report for it: phab:T417278. There is currently a fix up for review, so I hope it will be resolved soon. I'll post again here when I have an update. APaskulin (WMF) (talk) 16:54, 16 March 2026 (UTC)

Hi @Vibesolutions, The fix was deployed! I tested the app authentication flow locally, and I was able to get a valid token, so hopefully the issue is fixed for you as well. Let me know if you run into any other issues! APaskulin (WMF) (talk) 21:22, 16 March 2026 (UTC)