The EBSCOhost Entitlement API makes research easy by providing access to full text content from EBSCOhost full text databases.





Register a Client Application

Before you can begin the OAuth 2.0 process and receive your access token, you must register your App with the API.  This is necessary to provide the Authorization server with the following information:

  • Name of the App
  • A redirect or callback URL if needed.  A redirect or callback URL will redirect the user after the user has Authorized the data access. 

After registering the App, the App will have an assigned Client ID and Client Secret.  The Client ID is a public and unique identifier that will be used to identify the client application as an application.  The Client Secret is a private identifier kept secret between the App and the API.  The Client Secret is used to authenticate the App when it makes a request for an access token.

To Register an App:

  1. Log in to EBSCO Developer.
  2. Click on My Apps in the top navigation.
  3. Click on the Add a new App button at the top of the page.

    A form will appear.
  4. Enter the App Name in the field provided.
  5. Select the Type of App.
  6. Specify if the App needs access to user identities and/or details.
  7. Click the Product(s) desired.  The Callback URL, Customer ID and Group ID fields are optional.
  8. Click the Create App button.  You are returned to the My Apps page and your new App is listed.  Your new App will be Pending until your information has been reviewed and approved.  You will receive an email once your App has been Approved.
  9. Log in to EBSCO Developer once you receive your App Approval email.
  10. Navigate to the My Apps page.  The App status for your new App will show Approved.
  11. Click on the name of your application in the list.  The Credentials section is displayed.  Your application credentials, the Client ID and the Client Secret, are listed.
  12. Make note of the Client ID and Client Secret for the App.  Please use the Client ID and the Client Secret in the OAuth 2.0 process.