Introduction

MedsAPI Partners are consumers of any of the MedsAPI product endpoints on behalf of their customers. For subscription resellers, the partner makes a token request using the Customer ID and Group ID for a particular customer. The token is then cached for that user and used in all subsequent API calls for a particular product. The customer must have a subscription for the product. A different token must be created for each product that a customer wants to access. A content partner subscribes to the product content themselves and will use their own Client ID and Secret to obtain the content that they are subscribed to.

MedsAPI EBSCO Partner will use OAuth 2.0 for application credentials. Your application must use OAuth 2.0 to authorize requests. Every request to MedsAPI endpoints 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 general Getting Started or the OAuth 2.0 specification.

This section provides a brief overview of the process of getting an EBSCO Partner API token. It also describes details for using Dynamic Health partner APIs that provide access to bulk content often used for offline caching. Any of the MedsAPI endpoints for any product can be used, subject to what content the customer Id is subscribed to. If you have interacted with a RESTful API before, many of the concepts described here will be familiar to you.

Welcome to MedsAPI Partner!