This repository contains the code underlying a review of APIs that can be useful to social scientists. Thereby it provides explanations, code examples and research examples.
You can find the document here: APIs for social scientists: A collaborative review. The introduction explains how this project came about.
Paul C. Bauer (current Editor), Jan Behnert, Lion Behrens, Chung-hong Chan, Bernhard Clemm von Hohenberg, Lukas Isermann, Philipp Kadel, Melike N. Kaplan, Jana Klein, Markus Konrad, Barbara K. Kreis, Camille Landesvatter (current Editor), Madleen Meier-Barthold, Ondrej Pekacek, Pirmin Stöckle, Dean Lajic
→ Let us know! 📧
- You can learn about an API by writing about it 💡
- You can help others to dive more quickly and more easily into the world of APIs.
- Your name will appear as one of the contributors and as the main author for the corresponding chapter.
- Provide feedback and let us know where you got stuck
- Highlight or correct errors by raising issues or by creating pull requests
- Write another review chapter of an API (please contact us by Email beforehand)
- To do so please check out examples of the other chapters for the structure, length and code examples. (1) We will ask you to send a .rmd file with the API review of your choice. (2) Provide all references in bibtex format (to be included into 'references_overall.bib') and use corresponding bibtex keys in your chapter (e.g., 'Dobbrick2021-iz'). (3) Store/Cache data from your API call and make it available (e.g., RDS object, csv, etc.)
- In principle you should be able to compile the website locally after cloning/forking the repo.
- Add references to (your) published research examples that use the corresponding APIs
- To do so please check out the examples in the chapters. (1) Provide a short sentence indicating how/for what the API was used. (2) Provide the reference in bibtex format (see 'references_overall.bib') and the bibtex key you used (e.g., 'Dobbrick2021-iz').
- See corresponding issue for an overview of new and incoming chapters.
- Descriptions of and code examples for APIs are only useful when they are up to date. Our plan is to update chapters that are outdated, e.g., if an API version changes. Sometimes this might require adding new authors/contributors to a chapter if the original authors become inactive.
- A long list of public APIs: https://github.com/public-apis/public-apis