Make the most out of your custom discovery solution by connecting researchers to superior content and enhanced search features through Discovery API. Discovery API can also be used to configure discovery service funtionality.
Browse our guides to investigate use cases and find sample scenarios. Use our interactive sandbox to try the requests. Learn more about the operations, parameters and response details. Learn about how your applications can best use Discovery API to build your solution.
By integrating Discovery API into a system, library automation partners can build applications that can take advantage of leading features, including:
- Industry leading search with autocomplete
- Links to articles based on library holdings
- Support for multiple types of content
- Groups and profiles for different library departments
- Patron utilities such as citation exports
- Accessibility extensions to content
Discovery API uses OAuth 2.0 for application credentials. So, your application must use OAuth 2.0 to authorize requests. Every request to Discovery API must contain an access token that is determined by the OAuth 2.0 process. The access token is similar to an API Key in that it identifies your application to EBSCO. For more background on OAuth 2.0, please refer to the Getting Started section or the OAuth 2.0 specification.
This section provides a brief overview of the Discovery API core concepts. If you have interacted with a RESTful API before, many of the concepts described here will be familiar to you.