360 Services: XML APIs
- Product: 360 Core Client Center
Which ProQuest management and discovery services allow data access via APIs?
Our API (application programming interface) tools enable your institution to develop customized web services and local applications that can be used to enrich your patron-facing services. Depending on the individual API, you can implement these services as stand-alone web applications or as applications that interoperate with other services in your library. Each API is governed by specific Terms of Use (TOU) .
360 XML APIs
Our 360 XML APIs and Software Developer Kits (SDK) enable your library to design and develop your own user interfaces and web services. The APIs provide an interface for library tech teams to both send queries and receive XML-formatted results. Additionally, the APIs provide an administration interface which can be used to access information about e-resources -- including names, descriptions, and category.
With 360 XML APIs, you can:
- Maintain full control over your library's customizations without requiring the involvement of our Technical Library Support;
- Integrate our services smoothly into your own Web site;
- Build your own custom portals;
- Explore new ways of working with results, including embedding results in new locations outside the results page; and
- Work with SRU -- the leading standard protocol for Internet search queries -- and Dublin Core metadata.
Libraries that choose to use a 360 XML API have complete programmatic control over the application. Your development teams can build custom solutions to meet the requirements of local library staff.
Other libraries that already use our APIs may be willing to discuss different solutions they've created. For information about connecting with other libraries through our management and discovery listservs, see Client Listservs.
For details on an individual service and its API, click on the name of the service:
360 Link XML API: This API allows you to build a custom, OpenURL linking solution, based on the 360 Link service, so you can integrate OpenURL results smoothly into your own website.
360 Resource Manager -- Contact Importer API: This API allows libraries to build custom solutions for importing contact data to 360 Resource Manager. Libraries that opt to use the 360 Resource Manager Contact Importer API have complete programmatic control over the application's contact functionality.
360 Resource Manager License Data API: Allows you to retrieve and use the information that you store in the 360 Resource Manager License Manager tool to support a variety of use cases.
360 Resource Manager License Data API: Allows you to retrieve and use the information that you store in the 360 Resource Manager License Manager tool to support a variety of use cases.
Database Portal API: This API is only available to libraries that subscribe to 360 Search, and allows you to give visibility to the subject categories and associated resources that you have set up in 360 Search. For more information, send us a note using the Support Portal option.
Our Other APIs
Summon API: The Summon API provides access to search the Summon index and fetches real-time availability of catalog records.
Ulrichsweb API: The Ulrichsweb API is a simple HTTP based service that provides an interface for programmatic searching of the bibliographic records in Ulrichsweb. The output in XML or JSON can be used to integrate authoritative serials information into your library's website or your institution's other Ex Libris services.
Ulrich's XML Data Service: This is a SOAP-based data retrieval service that gives you the opportunity to subscribe to large amounts of Ulrich's raw data and use it for specific purposes under the terms of a customer-specific license agreement. This standalone subscription service is not part of the Ulrichsweb service.
- Date Created: 9-Feb-2014
- Last Edited Date: 15-Dec-2020
- Old Article Number: 9088