360 Link: XML API FAQ

Where can I find more information about the 360 Link XML API?

1. What is the 360 Link XML API?

   The 360 Link XML API allows libraries to build custom OpenURL linking solutions. The API provides a method for library tech teams to receive XML-formatted results of OpenURL queries against their electronic holdings, allowing them to display these results in whatever format they choose.

2. Is the API standards-based?

   Yes. The API was built to the OpenURL standard. Also, the XML results that are returned to the library are formatted using Dublin Core, the leading metadata standard in the world.

3. What are the benefits of the 360 Link XML API?

   • Maintain full control over your library's 360 Link customization without requiring the help of ProQuest Support Team.

   • Integrate 360 Link smoothly into your own website.

   • Explore new ways of working with OpenURL results.

   • Work with standards such as OpenURL and Dublin Core.

4. Is the API available for the Enhanced 360 Link with Index-Enhanced Direct Linking (IEDL), for legacy 360 Link, or for both?

   The 360 Link XML API is available for both.

5. How is this different from a standard 360 Link implementation?

   Libraries that opt to use the 360 Link API have complete programmatic control over the application. Development teams can build custom solutions to meet the requirements of local library staff. Additionally, developers can work to embed results in a variety of locations.

6. Who is the 360 Link XML API designed for?

   This service is designed for libraries with experienced software developers or development teams. If you are unsure if your library should be taking advantage of the XML API option at this time, then it may not yet be for you.

7. Does the API work with User Authentication turned on so that 360 Link access is controlled?

   Currently, the 360 Link XML API does not work with User Authentication. The API will not work if User Authentication is turned on.

8. How do I get started?

   If your library does not yet subscribe to 360 Link, you will first go through the customary service initiation with your ProQuest Account Representative. You will get a standard implementation of 360 Link, plus access to the XML API.

   If your library is already a 360 Link subscriber, let us know by using the Support Portal option and we will start the process of giving your library access to the API.

   To use or view the API, you library must first sign a Terms of Use (TOU). Upon completion of the TOU, you will be given access to the API technical documentation, which provide guidance about how to work with and use the API. Two PDF versions of the TOU agreement are available:

   • Use the Terms of Use document if internal staff from your institution will be using the API.

   • Use the Terms of Use (third party) document if an agent (a party not affiliated with your institution) will be using the API on your behalf.

   Use the Support Portal (accessible from the More Sites drop-down menu above) to send us a signed TOU agreement.

   Once a completed and signed TOU agreement has been received, we will provide you with a fully executed copy, and an API account will be configured for you.

9. How much does this service cost?

   This service is included with the cost of a subscription to 360 Link.

   For any further help, please contact us using the Support Portal.