API Portal apiportalwiki https://api.wikimedia.org/wiki/Main_Page MediaWiki 1.47.0-wmf.5 first-letter Media Special Talk User User talk API Portal API Portal talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk TimedText TimedText talk Module Module talk 1 143 2348 2276 2026-06-05T12:03:15Z Fuzheado 4505 /* Background */ Reply 2348 wikitext text/x-wiki Welcome to the discussion for the [[Community]] page! To leave a comment, [[Special:UserLogin|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": "<nowiki>https://mediawiki.org/wiki/HyperSwitch/errors/not_found#route</nowiki>", "title": "Not found.", "method": "get", "uri": "/en.wikipedia.org/v1/feed/featured/2025/03/28" } [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|talk]]) 07:35, 28 March 2025 (UTC) : Hi [[User:Alamin-dev|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 --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 20:55, 28 March 2025 (UTC) ::This is now fixed! Let me know if you run into any other issues. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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. [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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: [https://i.ibb.co.com/zTvZjgCr/Screenshot-2025-04-18-154452.png Screenshot link] [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|talk]]) 09:47, 18 April 2025 (UTC) : Hi [[User:Alamin-dev|Alamin]], Can you share the browser and the MediaWiki skin that you're using? --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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 [https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-the-current-and-next-generation-of-technical-contributors/ 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 [[meta:Special:OAuthConsumerRegistration/list|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 [[mw:Special:MyLanguage/Help:Watchlist|watchlist]] or subscribe to the [https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/ 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. --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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 [[mw:Wikimedia APIs|landing page]] (work in progress) on mediawiki.org. :* Starting in late March or early April 2026, api.wikimedia.org endpoints will have the same [[mw:Wikimedia APIs/Rate limits|rate limits]] as other Wikimedia APIs. The new rate limits are higher than the [[wikitech:API_Portal/Deprecation#API_Portal_historical_rate_limits|current rate limits]], so this change should not create any issues. The Lift Wing API will continue to have the same [[Lift Wing API/Rate limits|custom rate limits]] with only minor clarifications. :* For a timeline and the latest project information, see the [[wikitech:API_Portal/Deprecation|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 [[wikitech:Talk:API_Portal/Deprecation|project talk page]] :* Email techdocs[at]wikimedia.org :[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:39, 18 March 2026 (UTC) ::Can you please clarify this for the average person. Apologies if this is completely obvious to developers who live in this space. ::* Above, you say: "API Portal wiki will be inaccessible starting in June 2026" - It is now June 5, 2026. "api.wikimedia.org/wiki/Main_Page" is still accessible. Is this to be expected? ::* While you say "API Portal wiki will be in accessible," the top of the "Main page" says something slightly different: "'''Announcement''': The API Portal is shutting down in 2026. [[Talk:Community#Announcement: API Portal shutdown|Learn more]]" - Aren't "API Portal" and "API Portal wiki" two different things with two different fates? Is the wording in the "Announcement" accurate? Should it not say the "API Portal wiki" is shutting down in 2026? ::* I now see that the "Deprecation" page at [[wikitech:API_Portal/Deprecation]] has some more clarity, but it's still not entirely consistent with the messages here. While you say "The API Portal is shutting down in 2026" the table in Deprecation says no such thing – it simply says "api.wikimedia.org API endpoints" -> "Gradual deprecation." Is that deadline at the end of 2026 or is there some other update you can provide? ::* The only endpoint I can find for LiftWing is at "api.wikimedia.org/wiki/Lift_Wing_API" – is there something better yet at this point that will supersede it? if this, and other endpoints, are to be deprecated by the end of 2026, does that mean any coding solution against api.wikimedia.org are going to be out of date within 6 months? ::Thanks for any clarity here. I know it cannot be easy to un-consolidate these many different APIs. But as a community of practice, a lot of us are having a tough time figuring out what goes where. - [[User:Fuzheado|Fuzheado]] ([[User talk:Fuzheado|talk]]) 12:03, 5 June 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'''''"<nowiki>https://api.wikimedia.org/feed/v1/wikipedia/{lang}/featured/{y}/{m}/{d}</nowiki>"''' 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! [[User:Cholo5ntrol|Cholo5ntrol]] ([[User talk:Cholo5ntrol|talk]]) 17:30, 3 March 2026 (UTC) :Hi @[[User:Cholo5ntrol|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:03, 3 March 2026 (UTC) ::In the meantime, you can also call the Wikimedia Analytics API to [https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/reference/page-views.html#list-most-viewed-pages list the most-viewed pages] for a given day. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:06, 3 March 2026 (UTC) :::Hi @[[User:Cholo5ntrol|Cholo5ntrol]], This endpoint seems to be working as expected now. Let me know if you have any further issues. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 15:06, 4 March 2026 (UTC) ::::Thanks @[[User:APaskulin (WMF)|APaskulin (WMF)]]! Confirming that it's working as expected now. [[User:Cholo5ntrol|Cholo5ntrol]] ([[User talk: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. [[User:Vibesolutions|Vibesolutions]] ([[User talk:Vibesolutions|talk]]) 11:04, 13 March 2026 (UTC) :Hi @[[User:Vibesolutions|Vibesolutions]], Can you say more about which [[Authentication|authentication flow]] you're using? It will help us troubleshoot your issue. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 14:17, 13 March 2026 (UTC) ::Hey @[[User:APaskulin (WMF)|APaskulin (WMF)]]. I use the app authentication flow. ::The response is Internal Server Error 500. The response body is: ::<syntaxhighlight lang="html"> ::<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> ::</syntaxhighlight> ::Here is how i retrieve the token: ::<syntaxhighlight lang="typescript"> ::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; ::} ::</syntaxhighlight> ::the token retrieval works. But i can not call any api with that token. [[User:Vibesolutions|Vibesolutions]] ([[User talk:Vibesolutions|talk]]) 21:57, 13 March 2026 (UTC) :::Hi @[[User:Vibesolutions|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 16:54, 16 March 2026 (UTC) ::::Hi @[[User:Vibesolutions|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! [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 21:22, 16 March 2026 (UTC) 0zxse0wbdgasngrmf04pfms65wt5f2e 2349 2348 2026-06-05T12:04:25Z Fuzheado 4505 fix space 2349 wikitext text/x-wiki Welcome to the discussion for the [[Community]] page! To leave a comment, [[Special:UserLogin|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": "<nowiki>https://mediawiki.org/wiki/HyperSwitch/errors/not_found#route</nowiki>", "title": "Not found.", "method": "get", "uri": "/en.wikipedia.org/v1/feed/featured/2025/03/28" } [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|talk]]) 07:35, 28 March 2025 (UTC) : Hi [[User:Alamin-dev|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 --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 20:55, 28 March 2025 (UTC) ::This is now fixed! Let me know if you run into any other issues. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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. [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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: [https://i.ibb.co.com/zTvZjgCr/Screenshot-2025-04-18-154452.png Screenshot link] [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|talk]]) 09:47, 18 April 2025 (UTC) : Hi [[User:Alamin-dev|Alamin]], Can you share the browser and the MediaWiki skin that you're using? --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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 [https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-the-current-and-next-generation-of-technical-contributors/ 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 [[meta:Special:OAuthConsumerRegistration/list|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 [[mw:Special:MyLanguage/Help:Watchlist|watchlist]] or subscribe to the [https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/ 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. --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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 [[mw:Wikimedia APIs|landing page]] (work in progress) on mediawiki.org. :* Starting in late March or early April 2026, api.wikimedia.org endpoints will have the same [[mw:Wikimedia APIs/Rate limits|rate limits]] as other Wikimedia APIs. The new rate limits are higher than the [[wikitech:API_Portal/Deprecation#API_Portal_historical_rate_limits|current rate limits]], so this change should not create any issues. The Lift Wing API will continue to have the same [[Lift Wing API/Rate limits|custom rate limits]] with only minor clarifications. :* For a timeline and the latest project information, see the [[wikitech:API_Portal/Deprecation|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 [[wikitech:Talk:API_Portal/Deprecation|project talk page]] :* Email techdocs[at]wikimedia.org :[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:39, 18 March 2026 (UTC) ::Can you please clarify this for the average person. Apologies if this is completely obvious to developers who live in this space. ::* Above, you say: "API Portal wiki will be inaccessible starting in June 2026" - It is now June 5, 2026. "api.wikimedia.org/wiki/Main_Page" is still accessible. Is this to be expected? ::* While you say "API Portal wiki will be inaccessible," the top of the "Main page" says something slightly different: "'''Announcement''': The API Portal is shutting down in 2026. [[Talk:Community#Announcement: API Portal shutdown|Learn more]]" - Aren't "API Portal" and "API Portal wiki" two different things with two different fates? Is the wording in the "Announcement" accurate? Should it not say the "API Portal wiki" is shutting down in 2026? ::* I now see that the "Deprecation" page at [[wikitech:API_Portal/Deprecation]] has some more clarity, but it's still not entirely consistent with the messages here. While you say "The API Portal is shutting down in 2026" the table in Deprecation says no such thing – it simply says "api.wikimedia.org API endpoints" -> "Gradual deprecation." Is that deadline at the end of 2026 or is there some other update you can provide? ::* The only endpoint I can find for LiftWing is at "api.wikimedia.org/wiki/Lift_Wing_API" – is there something better yet at this point that will supersede it? if this, and other endpoints, are to be deprecated by the end of 2026, does that mean any coding solution against api.wikimedia.org are going to be out of date within 6 months? ::Thanks for any clarity here. I know it cannot be easy to un-consolidate these many different APIs. But as a community of practice, a lot of us are having a tough time figuring out what goes where. - [[User:Fuzheado|Fuzheado]] ([[User talk:Fuzheado|talk]]) 12:03, 5 June 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'''''"<nowiki>https://api.wikimedia.org/feed/v1/wikipedia/{lang}/featured/{y}/{m}/{d}</nowiki>"''' 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! [[User:Cholo5ntrol|Cholo5ntrol]] ([[User talk:Cholo5ntrol|talk]]) 17:30, 3 March 2026 (UTC) :Hi @[[User:Cholo5ntrol|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:03, 3 March 2026 (UTC) ::In the meantime, you can also call the Wikimedia Analytics API to [https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/reference/page-views.html#list-most-viewed-pages list the most-viewed pages] for a given day. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:06, 3 March 2026 (UTC) :::Hi @[[User:Cholo5ntrol|Cholo5ntrol]], This endpoint seems to be working as expected now. Let me know if you have any further issues. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 15:06, 4 March 2026 (UTC) ::::Thanks @[[User:APaskulin (WMF)|APaskulin (WMF)]]! Confirming that it's working as expected now. [[User:Cholo5ntrol|Cholo5ntrol]] ([[User talk: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. [[User:Vibesolutions|Vibesolutions]] ([[User talk:Vibesolutions|talk]]) 11:04, 13 March 2026 (UTC) :Hi @[[User:Vibesolutions|Vibesolutions]], Can you say more about which [[Authentication|authentication flow]] you're using? It will help us troubleshoot your issue. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 14:17, 13 March 2026 (UTC) ::Hey @[[User:APaskulin (WMF)|APaskulin (WMF)]]. I use the app authentication flow. ::The response is Internal Server Error 500. The response body is: ::<syntaxhighlight lang="html"> ::<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> ::</syntaxhighlight> ::Here is how i retrieve the token: ::<syntaxhighlight lang="typescript"> ::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; ::} ::</syntaxhighlight> ::the token retrieval works. But i can not call any api with that token. [[User:Vibesolutions|Vibesolutions]] ([[User talk:Vibesolutions|talk]]) 21:57, 13 March 2026 (UTC) :::Hi @[[User:Vibesolutions|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 16:54, 16 March 2026 (UTC) ::::Hi @[[User:Vibesolutions|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! [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 21:22, 16 March 2026 (UTC) puy7aqhp4u8kii525n10v6jq02u23y4 2350 2349 2026-06-05T16:35:04Z APaskulin (WMF) 20 /* Background */ Reply 2350 wikitext text/x-wiki Welcome to the discussion for the [[Community]] page! To leave a comment, [[Special:UserLogin|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": "<nowiki>https://mediawiki.org/wiki/HyperSwitch/errors/not_found#route</nowiki>", "title": "Not found.", "method": "get", "uri": "/en.wikipedia.org/v1/feed/featured/2025/03/28" } [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|talk]]) 07:35, 28 March 2025 (UTC) : Hi [[User:Alamin-dev|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 --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 20:55, 28 March 2025 (UTC) ::This is now fixed! Let me know if you run into any other issues. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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. [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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: [https://i.ibb.co.com/zTvZjgCr/Screenshot-2025-04-18-154452.png Screenshot link] [[User:Alamin-dev|Alamin ]] ([[User talk:Alamin-dev|talk]]) 09:47, 18 April 2025 (UTC) : Hi [[User:Alamin-dev|Alamin]], Can you share the browser and the MediaWiki skin that you're using? --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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 [https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-the-current-and-next-generation-of-technical-contributors/ 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 [[meta:Special:OAuthConsumerRegistration/list|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 [[mw:Special:MyLanguage/Help:Watchlist|watchlist]] or subscribe to the [https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/ 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. --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk: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 [[mw:Wikimedia APIs|landing page]] (work in progress) on mediawiki.org. :* Starting in late March or early April 2026, api.wikimedia.org endpoints will have the same [[mw:Wikimedia APIs/Rate limits|rate limits]] as other Wikimedia APIs. The new rate limits are higher than the [[wikitech:API_Portal/Deprecation#API_Portal_historical_rate_limits|current rate limits]], so this change should not create any issues. The Lift Wing API will continue to have the same [[Lift Wing API/Rate limits|custom rate limits]] with only minor clarifications. :* For a timeline and the latest project information, see the [[wikitech:API_Portal/Deprecation|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 [[wikitech:Talk:API_Portal/Deprecation|project talk page]] :* Email techdocs[at]wikimedia.org :[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:39, 18 March 2026 (UTC) ::Can you please clarify this for the average person. Apologies if this is completely obvious to developers who live in this space. ::* Above, you say: "API Portal wiki will be inaccessible starting in June 2026" - It is now June 5, 2026. "api.wikimedia.org/wiki/Main_Page" is still accessible. Is this to be expected? ::* While you say "API Portal wiki will be inaccessible," the top of the "Main page" says something slightly different: "'''Announcement''': The API Portal is shutting down in 2026. [[Talk:Community#Announcement: API Portal shutdown|Learn more]]" - Aren't "API Portal" and "API Portal wiki" two different things with two different fates? Is the wording in the "Announcement" accurate? Should it not say the "API Portal wiki" is shutting down in 2026? ::* I now see that the "Deprecation" page at [[wikitech:API_Portal/Deprecation]] has some more clarity, but it's still not entirely consistent with the messages here. While you say "The API Portal is shutting down in 2026" the table in Deprecation says no such thing – it simply says "api.wikimedia.org API endpoints" -> "Gradual deprecation." Is that deadline at the end of 2026 or is there some other update you can provide? ::* The only endpoint I can find for LiftWing is at "api.wikimedia.org/wiki/Lift_Wing_API" – is there something better yet at this point that will supersede it? if this, and other endpoints, are to be deprecated by the end of 2026, does that mean any coding solution against api.wikimedia.org are going to be out of date within 6 months? ::Thanks for any clarity here. I know it cannot be easy to un-consolidate these many different APIs. But as a community of practice, a lot of us are having a tough time figuring out what goes where. - [[User:Fuzheado|Fuzheado]] ([[User talk:Fuzheado|talk]]) 12:03, 5 June 2026 (UTC) :::Hi @[[User:Fuzheado|Fuzheado]], Thanks for your feedback! My apologies that things haven't been clear. :::* Yes, it's expected. We're planning to start the process of making the API Portal inaccessible later this month. We don't have an exact date yet since we're still working on creating a new location for the Lift Wing API docs. Once those docs are complete, I'll send an update with the exact dates. :::* If I understand correctly, you're understanding the API Portal wiki to be the site itself while the API Portal in general includes the endpoints and other functionality. That makes sense to me. I'll update the banner on the main page to specify that the wiki itself is shutting down. :::* I see the confusion that you're referring to with this. The API Portal wiki is shutting down this month. The api.wikimedia.org API endpoints will continue to work after the API Portal wiki is shut down. Eventually, these endpoints will be deprecated and migrated to new URLs, but unfortunately, I don't have a specific timeline for this process yet. The project to create the new API URLs that will replace the api.wikimedia.org APIs is scheduled for sometime between July 2026 and March 2027. Once these new API URLs are ready to use, we'll start a deprecation process for the api.wikimedia.org APIs. This process will include several months for developers to migrate to the new API URLs before the api.wikimedia.org APIs stop working. :::* Unfortunately, that is correct. Any coding solution that uses api.wikimedia.org endpoints will be out of date eventually, and we don't yet know what the new API endpoints are that developers will need to migrate to. However, we are committed to helping developers as much as we can during the migration process. We'll be looking at the usage of the api.wikimedia.org API endpoints and trying to reach out to developers proactively so no one is surprised. My guess is that the api.wikimedia.org endpoints won't be fully deprecated until mid-2027, but I wanted to be conservative about the documented timeline since it could happen by the end of 2026, as you said. The best thing to do for now is to subscribe to one of the communication channels listed on the [[wikitech:API_Portal/Deprecation#Updates|Wikitech page]] to get the latest updates. I'll be updating those channels as soon as I know more. :::I definitely agree that is difficult to figure out what goes where. For now, the best source of API documentation is [[mw:Wikimedia APIs]]. :::Thanks again for this feedback. It's really helpful! I've made some small updates to the [[wikitech:API_Portal/Deprecation|Wikitech page]] to help clarify some of this, but let me know if you have any other questions or feedback. Once the API Portal wiki is shut down, you can always reach me via the [[wikitech:Talk:API_Portal/Deprecation|Wikitech talk page]]. --[[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 16:35, 5 June 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'''''"<nowiki>https://api.wikimedia.org/feed/v1/wikipedia/{lang}/featured/{y}/{m}/{d}</nowiki>"''' 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! [[User:Cholo5ntrol|Cholo5ntrol]] ([[User talk:Cholo5ntrol|talk]]) 17:30, 3 March 2026 (UTC) :Hi @[[User:Cholo5ntrol|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:03, 3 March 2026 (UTC) ::In the meantime, you can also call the Wikimedia Analytics API to [https://doc.wikimedia.org/generated-data-platform/aqs/analytics-api/reference/page-views.html#list-most-viewed-pages list the most-viewed pages] for a given day. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 18:06, 3 March 2026 (UTC) :::Hi @[[User:Cholo5ntrol|Cholo5ntrol]], This endpoint seems to be working as expected now. Let me know if you have any further issues. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 15:06, 4 March 2026 (UTC) ::::Thanks @[[User:APaskulin (WMF)|APaskulin (WMF)]]! Confirming that it's working as expected now. [[User:Cholo5ntrol|Cholo5ntrol]] ([[User talk: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. [[User:Vibesolutions|Vibesolutions]] ([[User talk:Vibesolutions|talk]]) 11:04, 13 March 2026 (UTC) :Hi @[[User:Vibesolutions|Vibesolutions]], Can you say more about which [[Authentication|authentication flow]] you're using? It will help us troubleshoot your issue. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 14:17, 13 March 2026 (UTC) ::Hey @[[User:APaskulin (WMF)|APaskulin (WMF)]]. I use the app authentication flow. ::The response is Internal Server Error 500. The response body is: ::<syntaxhighlight lang="html"> ::<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> ::</syntaxhighlight> ::Here is how i retrieve the token: ::<syntaxhighlight lang="typescript"> ::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; ::} ::</syntaxhighlight> ::the token retrieval works. But i can not call any api with that token. [[User:Vibesolutions|Vibesolutions]] ([[User talk:Vibesolutions|talk]]) 21:57, 13 March 2026 (UTC) :::Hi @[[User:Vibesolutions|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. [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 16:54, 16 March 2026 (UTC) ::::Hi @[[User:Vibesolutions|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! [[User:APaskulin (WMF)|APaskulin (WMF)]] ([[User talk:APaskulin (WMF)|talk]]) 21:22, 16 March 2026 (UTC) rla9a9ycjqz6kgtvpcy1fni0gk6fmv2 8 213 2351 2190 2026-06-05T16:35:38Z APaskulin (WMF) 20 Clarify language 2351 wikitext text/x-wiki '''Announcement''': The API Portal wiki is shutting down in 2026. [[Talk:Community#Announcement:_API_Portal_shutdown|Learn more]] 6gpgxwm799aranrdh2teu1os0imlbqp