According to its website, an unAPI is:
a tiny HTTP API any web application may use to co-publish discretely identified objects in both HTML pages and disparate bare object formats. It consists of three parts: an identifier microformat, an HTML autodiscovery link, and three HTTP interface functions, two of which have a standardized response format.
The unAPI specification is only two pages long.[1]
Server-side applications which use unAPI
- Bebop
- Evergreen
- Koha
- refbase[2]
- WordPress (via a plugin)
- VITAL, digital repository
- invenio digital library framework
- Omeka S, web-publishing platform for academic and cultural repositories
- Glottolog a clld app supports unAPI on its root page.
Client tools which can use unAPI
See also
References
- ^ "Introducing UnAPI". Ariadne. ' (48). 2006-07-30. Archived 2020-11-09 at the Wayback Machine. Retrieved 2017-07-11.
- ^ "UnAPI service". refbase. Archived 2020-11-09 at the Wayback Machine. Retrieved 2020-11-09.
Further reading
- Koster, James (ed.) (2012-03-19). "unAPI: an un-API for webapps - A super-simple way to get stuff". refbase. Archived 2014-12-18 at the Wayback Machine. Retrieved 2020-11-09.
- Koster, James (ed.) (2006-07-23 [2006-01-14]). "contribution". unAPI Version 1 (normative). 1.0. Archived 2014-03-31 at the Wayback Machine.