The OpenAIRE APIs

Our APIs can be accessed anonymously and are free of charge. Higher rate limits are available for signed in users and registered services. For more information please check here.

Broker

API to enrich metadata for repositories, publishers and aggregators.

Documentation
Swagger

ScholeXplorer

Access to links between dataset and literature objects and dataset and dataset objects.

REST APIs Documentation
ScholeXplorer dump schema
ScholeXplorer dump

For Bulk Access

The OpenAIRE APIs is intended for metadata discovery and exploration only, that is it does not give direct access to publication files and it does not provide access to the whole information space.

TERMS OF USE AND SLA

OpenAIRE HTTP API: the APIs are free-to-use (no sign-up needed) by any third-party service. Note that:

  • The OpenAIRE APIs can be accessed over HTTPS both by authenticated and unauthenticated requests. To achieve better rate limits you need to make authenticated requests. For more information check the documentation here
  • For accessing the whole content of the OpenAIRE Graph check the OpenAIRE Graph Dumps.
  • Since 2015 an RDF dump of the LOD is made available in Zenodo.org, but the respective service has been discontinued and no new OpenAIRE LOD Dump versions will be released in the future.

Quality of service: all API services are running in production 24/7 within the OpenAIRE infrastructure premises deployed at the data center facilities of the Interdisciplinary Centre for Mathematical and Computational Modelling (ICM).

OpenAIRE Graph license is CC-BY: the records returned by the service can be freely re-used by commercial and non-commercial partners under CC-BY license, hence as long as OpenAIRE is acknowledged as a data source.

OpenAIRE HTTP API: the APIs are free-to-use (no sign-up needed) by any third-party service.
For more details on the rate limits, please check here.
For any questions please contact us.

How to cite the graph

If you use the OpenAIRE APIs please cite the OpenAIRE Graph following the recommendation available here.

RESPONSE METADATA FORMAT

For more details on this, please check here.

API documentation changes

For the list of changes to this documentation click here