In this topic
The Content Delivery API contains five NuGet packages:
Depending on specific scenarios, one or several packages can be installed. For example:
If the Content Delivery API runs on the same domain and in the same server context as the regular site, and the purpose is to use it along with frameworks like React or Vue to build the front-end, the EPiServer.ContentDeliveryApi.Cms package should be installed.
For this scenario, Content Delivery API can work well with cookie-based authentication (for example, using the default login form of the Alloy site), so there is no need of installing EPiServer.ContentDeliveryApi.OAuth package for token-based authentication and authorization.
If searching functionalities should be enhanced within the site, EPiServer.ContentDeliveryApi.Search package should be installed. This package basically connects the site to Episerver Search & Navigation (formerly Episerver Find) through endpoints.
If the purpose is to build front-end on mobile platforms, EPiServer.ContentDeliveryApi should be chosen. The ContentDeliveryApi.OAuth package provides an endpoint to obtain token and later on, this token is used for authentication and authorization for requests acquiring resources.
Follow these steps to upgrade the Content Delivery API if the site has installed versions 1.0.0 or 1.0.1:
Last updated: Nov 08, 2018