Web APIs hub
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date.
Web APIs Hub
A central place for third-party developers to use Wikimedia web APIs
The Web APIs Hub invites new and experienced developers to try Wikimedia web APIs in a friendly environment.
Wikimedia has made its APIs freely available, but for external developers it is difficult to figure out what they can do with our APIs, and how. Our web APIs and their documentation are currently scattered across several projects, with no central location for people to learn about and build upon them. This is the problem the Web APIs hub wants to solve.
The main target audience for this hub are developers not developing, or even running, the MediaWiki software. We want to diminish the risk of confusing them by mixing the content relevant to them with the rest of mediawiki.org. We plan to address this risk by morphing the API: namespace into the Web APIs hub, controlling and contextualizing links to other part of mediawiki.org or other Wikimedia sites. We also want to try offering a different look & feel in this namespace.
See also the ongoing list of requirements (under discussion).
Check the Phabricator board where we are tracking all the tasks: #Web-APIs-Hub. Our goals for October-December 2015 are to:
- Map current use of Wikimedia web APIs (phab:T114017) to guide where to focus documentation effort. In addition to this analytics work, we welcome your feedback on what you find difficult or confusing.
- Write more articles (anyone can help, see /Contributing)
The hub is divided into three sections:
- Inspire: where cool projects are showcased; links to more detailed project description pages
- Explore: where users can play with the API(s) in functional sandboxes
- /Build: where all the static official documentation and pointers to data sets reside.
phab:T102079 "Metrics about the use of the Wikimedia web APIs"
We also have stats related to engagement with www.mediawiki.org. We want to filter these down to the API: (and possibly Manual:) namespace.
- https://stats.wikimedia.org/wikispecial/EN/ChartsWikipediaMEDIAWIKI.htm shows page views and edits for mediawiki.org (scroll right to see 2014-2015), but these aren't broken down by namespace
- https://stats.wikimedia.org/wikispecial/EN/TablesWikipediaMEDIAWIKI.htm has various interesting counts for www.mediawiki.org, including recently active editors
- You can get page views from stats.grok.se, e.g. API:Web APIs hub page views in the last 90 days. Note mediawiki.org isn't in the http://stats.grok.se dropdown (phab:T111662).
- Ankita, mobile developer willing to use Wikimedia data to enhance mobile apps.
- Alberto, data scientist employed at an organization gathering and releasing data that could be synced with Wikimedia's.
- Reetta, cultural activist working on mass-upload activities for public institutions.
- Yanhui, academic researcher needing a massive data set to sustain his thesis.
These represent the users we want to make happy first (phab:T92941)
- A curated collection of projects created using data from Wikimedia projects.
- Means of submitting a project to be considered for showcase.
- Documentation at different technical levels.
- An organized list of APIs and datasets available.
- Way of requesting new datasets and/or APIs.
- Related news, features, and announcements.
- A way for the community to get in touch with WMF folks for help on projects.
- Possibility to customize the UI in order to provide a pleasant user experience.
- Possibility to create and edit content comfortably, including the homepage, tutorials, project showcases, code examples and screenshots.
- Possibility to export API documentation from source code in repositories.
- Possibility to integrate API sandboxes.
- Possibility to search all the content at once.
- Possibility to translate manual documentation (not the strict API docs)
Internal resources for developers
The following is a list of resources housed across multiple locations to help developers build using Wikimedia data. Feel free to add to the list below.
- /w/api.php output (self-documenting MediaWiki entry point on every wiki)
- https://www.mediawiki.org/wiki/API:Client_code/Gold_standard (best practices for web API client library development)
- Wikimedia Design Style Guide with user-interface focus
- OOUI – standard user-interface library documentation and demos
- various text files and sample HTML in core/docs
- Recent changes stream Done Web APIs hub article
- The MediaWiki web API. It's self-documenting (Special:APIHelp) and has a sandbox. Most Wikimedia APIs are implemented as API actions or query submodules of the MediaWiki web API, including:
- RESTBase (new). It's self-documenting (enwiki starting point) with a built-in sandbox
- Parsoid API
- Pageview API . Based on RESTBase, also self-documenting (root of the endpoints available).
- Language API (?)
- Account Creation API (new?, was part of abandoned Extension:SignupAPI)
Other internal(ish) projects
- API:Client code (third-party client libraries for the MediaWiki web API)
- API:Client code/Evaluations Features, maintenance status, documentation.
Developer hubs & API documentation
Best in Class human readable API documentation
New York Times
- https://www.quora.com/Data/Where-can-I-find-large-datasets-open-to-the-public (big list)
- http://www.reddit.com/r/datasets (another big list)