Hypothesis owner: @apaskulin
Hypothesis owner delegate: @HCoplin-WMF
Start date: April 6, 2026
Target completion date: June 30, 2026
Actual completion date: June 30, 2026
Hypothesis ID: 5.2.11b
If we complete API Portal documentation migration, we will be able to fully deprecate the API Portal system, which will simplify API documentation discovery, increase documentation consistency, and reduce the number of API support systems.
Scope
In scope:
- Documentation on api.wikimedia.org
- Documentation for APIs available through api.wikimedia.org
April-June project plan
- Migrate Lift Wing API docs
- T419455: Generate OpenAPI descriptions for Lift Wing APIs
- Redirect API Portal pages
- Update links on other wikis
- Submit patches for links in code repositories
- Declined tasks related to the API Portal on wiki (except tasks related to OAuth UX for reference in the short term)
- T415923: Plan shutdown process for the API Portal
- Send general reminders (API Portal, tech news, wikitech-l, mediawiki-api-announce) (target date: June 11)
- T427537: Close the API Portal wiki (completed on June 15)
- T418492: Redirect API Portal wiki URLs to www.mediawiki.org/wiki/Wikimedia_APIs (completed on June 22)
- T429372: Remove API Portal from WMF MediaWiki config
- Archive related components
- Mark wiki pages for the API Portal and the API Gateway as historical
- T418494: Delete the API Portal wiki (started on June 23)
Next steps:
- Continue work on cleanup tasks related to T418494: Delete the API Portal wiki
- T429394: Serve Lift Wing OpenAPI description as a single file
- T430701: Remove unused config for wgRestAllowCrossOriginCookieAuth
April-June outcomes
- Lift Wing API reference documentation: https://www.mediawiki.org/w/index.php?api=lift-wing&title=Special%3ARestSandbox
- API Portal deprecation project page: https://wikitech.wikimedia.org/wiki/API_Portal/Deprecation
- Redirected all API Portal wiki URLs to the Wikimedia APIs page on mediawiki.org
- Updated all links to API Portal wiki URLs on wiki pages and in code repositories
- Deleted the API Portal wiki from Wikimedia infrastructure, including removing 92 lines of code from the mediawiki-config repository and improving the overall process for deleting a wiki
- Archived the API Portal skin and extension, reducing the number of components that WMF maintains in production
API Portal components
API Portal components:
- Wiki instance (API Portal content audit)
- Skin:WikimediaApiPortal (used only on the API Portal)
- Extension:WikimediaApiPortalOAuth duplicating functionality provided by Extension:OAuth (used only on the API Portal)
- Phabricator projects: API Portal, Wikimedia API Portal, MediaWiki-extensions-WikimediaApiPortalOAuth
Related components:
- API Gateway Envoy instance (to be deprecated; see T413438)
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. We’re still working on exact plans and schedules for shutting down the Portal, 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.
Information architecture
- mw:Wikimedia APIs – main landing page for Wikimedia APIs
- mw:Wikimedia APIs/subpages – topics that apply to multiple APIs
- mw:[API name] API – landing pages for an individual API
- mw:[API name] API/subpages – topics that apply to an individual API
- mw:[tutorial name] – API tutorials
- wikitech:API Portal/Deprecation – Information about deprecated api.wikimedia.org functionality. We can use this as an intermediary source of information to direct users to docs for API Portal APIs that are available elsewhere.
All APIs in the collection will have a landing page on mediawiki.org that uses this structure for consistency, but if those docs already exist on another wiki, the docs themselves can remain there instead of being migrated to mediawiki.org.
Links to the API Portal on other wikis
- https://wikitech.wikimedia.org/wiki/Special:LinkSearch?target=api.wikimedia.org
- https://www.mediawiki.org/w/index.php?title=Special:LinkSearch&limit=50&offset=0&target=api.wikimedia.org
- https://meta.wikimedia.org/w/index.php?title=Special:LinkSearch&limit=50&offset=0&target=api.wikimedia.org
- https://www.wikifunctions.org/w/index.php?limit=100&fulltext=1&ns0=1&ns100=1&ns102=1&ns104=1&ns106=1&ns12=1&profile=advanced&search=insource%3A%2F%22api.wikimedia.org%22%2F&title=Special%3ASearch&searchToken=dcj276v1gymvv4tfgixfo4jg9
- https://www.mediawiki.org/w/index.php?limit=100&fulltext=1&ns0=1&ns100=1&ns102=1&ns104=1&ns106=1&ns12=1&profile=advanced&search=insource%3A%2F%22api.wikimedia.org%22%2F&title=Special%3ASearch&searchToken=spbtbtp5ulqncx00rfkftiqt
- https://wikitech.wikimedia.org/w/index.php?limit=100&fulltext=1&ns0=1&ns100=1&ns102=1&ns104=1&ns106=1&ns12=1&profile=advanced&search=insource%3A%2F%22api.wikimedia.org%22%2F&title=Special%3ASearch&searchToken=spbtbtp5ulqncx00rfkftiqt
- https://meta.wikimedia.org/w/index.php?limit=100&fulltext=1&ns0=1&ns100=1&ns102=1&ns104=1&ns106=1&ns12=1&profile=advanced&search=insource%3A%2F%22api.wikimedia.org%22%2F&title=Special%3ASearch&searchToken=spbtbtp5ulqncx00rfkftiqt
January-March hypothesis
Hypothesis owner: @apaskulin
Hypothesis owner delegate: @HCoplin-WMF
Start date: January 12, 2026
Target completion date: March 27, 2026
Actual completion date: April 2, 2026
Hypothesis ID: WE5.2.11
If we experiment and establish processes for standardizing documentation currently in the API Portal, we can consolidate sources of information and improve documentation consistency.
January-March project plan
- Communications and planning
- Phase 1 communications (basic announcement)
- Post to API Portal
- Talk:Community
- Talk:Contributing
- Site banner
- Notices on Community and Maintainers pages
- wikitech:API Portal
- WMF internal Slack
- Post to API Portal
- Phase 2 communications (target date: March 17)
- Draft content
- Review with stakeholders
- Channels: API Portal, tech news, wikitech-l, mediawiki-api-announce
- User outreach (documentation editors group, user page editors, talk page editors)
- Phase 1 communications (basic announcement)
- Content migration
- Migrate docs for individual APIs
- Migrate general API docs
- Decide on information architecture (IA)
- Projects and languages
- Reusing free content
- Stability policy
- Best practices for bots and tools
- Use cases
- API guidelines: Archived to Wikitech
- Authentication guide
- Security best practices
- Rate limits
- Conditional requests
- Check for links to the API Portal on all wikis
January-March outcomes
- New central landing page: https://www.mediawiki.org/wiki/Wikimedia_APIs
- Subpages: https://www.mediawiki.org/wiki/Special:PrefixIndex?prefix=Wikimedia+APIs&namespace=0&hideredirects=1&stripprefix=1
- Navigation template: https://www.mediawiki.org/wiki/Template:Wikimedia_APIs (marked for translation)
- New or updated API landing pages
- https://www.mediawiki.org/wiki/Wikifunctions_API
- https://www.mediawiki.org/wiki/Wikimedia_REST_API
- https://www.mediawiki.org/wiki/Link_Recommendation_API
- https://www.mediawiki.org/wiki/Page_Description_API
- https://www.mediawiki.org/wiki/Wikifeeds_API
- https://wikitech.wikimedia.org/wiki/Machine_Learning/LiftWing/API
- Updated OpenAPI descriptions
- Updated API documentation standards: https://www.mediawiki.org/wiki/Documentation/API_documentation
- Quick start for new APIs: https://www.mediawiki.org/wiki/Documentation/API_documentation#Quickstart
- API landing page format: https://www.mediawiki.org/wiki/Documentation/API_documentation#Landing_page
- API infobox template: https://www.mediawiki.org/wiki/Template:Wikimedia_API (marked for translation)
- Evaluation of APIs against documentation standards: https://www.mediawiki.org/wiki/Wikimedia_Technical_Documentation_Team/API_documentation_strategy/Gaps
- API Portal deprecation project page: https://wikitech.wikimedia.org/wiki/API_Portal/Deprecation
- Content migration tracker: https://docs.google.com/spreadsheets/d/11ec2IR0V99clEDn6B9I8TZadmXEwRc6Ep1LPM_L_BjE/edit?gid=0#gid=0
- Communications:
- https://api.wikimedia.org/wiki/Talk:Community#Announcement:_API_Portal_shutdown
- https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/V3PIQKCZCFFHX3ODZNJ3DTTGZ3YNNCDM/
- https://lists.wikimedia.org/hyperkitty/list/mediawiki-api-announce@lists.wikimedia.org/thread/YJBNM4ABEZT5ZMLQJBRNVVPY7K46HNI4/
- https://meta.wikimedia.org/wiki/Tech/News/2026/13
Resources
- https://techblog.wikimedia.org/2025/06/12/apis-as-a-product-investing-in-the-current-and-next-generation-of-technical-contributors/
- https://wikitech.wikimedia.org/wiki/API_Portal/Retrospective
- https://wikitech.wikimedia.org/wiki/Delete_a_wiki
- “Usually, wikis are closed, not deleted.”
- Example of a deleted wiki: https://meta.wikimedia.org/wiki/Sep11wiki
- “It was made read-only in September 2006[1], and later deleted from Wikimedia entirely in early 2007, but remains available on the Wayback Machine, and backups of the database are still available on the Wikimedia dumps site and on the Internet Archive.”
- https://meta.wikimedia.org/wiki/Closing_projects_policy
- https://wikitech.wikimedia.org/wiki/Close_a_wiki
- https://meta.wikimedia.org/wiki/Proposals_for_closing_projects
- “The [deleted] wiki should be redirected to another URL”
- https://meta.wikimedia.org/wiki/Closed_wiki
- https://noc.wikimedia.org/conf/dblists/closed.dblist
- Example of a closed wiki: https://transitionteam.wikimedia.org/wiki/Main_Page
- Undeployment