In addition to the web interface, the open access monitor offers an open REST API, which is available at https://api.open-access-monitor.de/.
In addition to the web interface, the open access monitor offers an open REST API, which is available at [REST-API](https://open-access-monitor.de/api). All public data of the monitor can be queried.
# Data query
This end point is required for data query:
`/data/{database}`
So far only "public" can be used as database`. The query is passed by `query` parameter. The following [MongoDB-Commands](https://www.mongodb.com/docs/manual/reference/command/) are supported by the API:
All API answers are formatted according to the answers of the MongoDB.
The entities are described [here](https://jugit.fz-juelich.de/synoa/oam-dokumentation/-/wikis/English%20Version/Open%20Access%20Monitor/Database%20Schema). Possible collections for queries:
* Publications
* PublicationCosts
* Journals
* Publishers
* Organisations
The previous week’s data is stored in additional collections with the suffix `_old`, which are updated every Sunday. With this endpoint and without a query parameter a list of all collections can be obtained.
The OA Categories are encoded as numbers as shown in this table: [OA Categories](https://jugit.fz-juelich.de/synoa/oam-dokumentation/-/wikis/English%20Version/Open%20Access%20Monitor/OA%20Categories)
We offer [Swagger](https://open-access-monitor.de/api/swagger), because all endpoints can be seen and tried there.
# Terms of use
We have a fair use policy for the API. Although there are no fixed quotas, we reserve the right to take appropriate measures should we notice above-average utilization. If you are planning very large queries, please consult us in advance.
The technical documentation of the possible endpoints can be found at https://api.open-access-monitor.de/swagger/.