Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

Apr 28, 2023
(3 votes)

Content Delivery / Headless API Implementation


I was new to the Headless (CD) implementation and learned with the help of existing resources and implemented it successfully for our requirement, so thought of sharing the implementation steps, in case anyone looking for step by step Content Delivery API implementation or Headless Implementation.

 Below are the tools/platforms I 've used for the implementation,

  1. CMS 11 
  2. React 
  3. ContentDeliveryApi.Cms 2.21.1

Step: 1

Install the below packages through the NuGet package manager.

<package id="EPiServer.ContentDeliveryApi" version="2.19.0" targetFramework="net48" />
  <package id="EPiServer.ContentDeliveryApi.Cms" version="2.21.1" targetFramework="net48" />
  <package id="EPiServer.ContentDeliveryApi.Core" version="2.21.1" targetFramework="net48" />
  <package id="EPiServer.ContentDeliveryApi.Forms" version="2.21.1" targetFramework="net48" />

Step: 2

Add the below configs into web.config, I'm not sure 100% knowledge on why this is required but either of those configs should be set to true, and the other one should be set to false, and not both of them set to true or false.

 <add key="episerver:contentdeliverysearch:maphttpattributeroutes" value="true" />
    <add key="episerver:contentdelivery:maphttpattributeroutes" value="false" />

Step: 3

Add a new Initialization module,

using EPiServer.ContentApi.Cms;
using EPiServer.ContentApi.Core.Configuration;
using EPiServer.Framework;
using EPiServer.Framework.Initialization;
using EPiServer.ServiceLocation;
using System;
using System.Linq;

namespace Alloy.Web.Admin.ContentDeliveryApi
    public class ContentDeliveryApiInit : IConfigurableModule
        public void ConfigureContainer(ServiceConfigurationContext context)
            context.Services.Configure<ContentApiConfiguration>(config => {

        public void Initialize(InitializationEngine context)
            //Add initialization logic, this method is called once after CMS has been initialized

        public void Uninitialize(InitializationEngine context)
            //Add uninitialization logic

Once you are done with the above steps you can re-build and run your solution to verify everything okay with the solution.

If you see your solution is working fine, then you can test Content Delivery API by accessing a site content with the help of Visual Studio Code(I feel it's a very feasible tool to access Headless content), In case if you don't have a REST Client in your Visual Studio Code please install the below Extension, It's really useful during our Headless implementation to test content.


To get site definitions:


To get your page content:


To Expand the Content Area/Content reference within Content: 

To Get Language-Specific Content: 
In this way, your content is ready to access through Content Delivery API.
Step 4:
If you above all are working as expected we can move on to the next step.
The next will be creating the Content type, ViewModel, Controller, Basic view, and React development for fetching data and rendering data.
In my case had to create all of the above from scratch, maybe your case may differ. So I like to cover those parts in another blog. 
Please feel free to add your comments, questions, thoughts, or any missing steps.
Thanks for reading. Have a good day. 
Apr 28, 2023


Manoj Kumawat
Manoj Kumawat May 2, 2023 02:23 PM

Nice! Would be a good idea to write on Search & Navigation usages with ContentSearch.Api next ?

Please login to comment.
Latest blogs
Join the Work Smarter Webinar: Working with the Power of Configured Commerce (B2B) Customer Segmentation December 7th

Join this webinar and learn about customer segmentation – how to best utilize it, how to use personalization to differentiate segmentation and how...

Karen McDougall | Dec 1, 2023

Getting Started with Optimizely SaaS Core and Next.js Integration: Creating Content Pages

The blog post discusses the creation of additional page types with Next.js and Optimizely SaaS Core. It provides a step-by-step guide on how to...

Francisco Quintanilla | Dec 1, 2023 | Syndicated blog

Stop Managing Humans in Your CMS

Too many times, a content management system becomes a people management system. Meaning, an organization uses the CMS to manage all the information...

Deane Barker | Nov 30, 2023

A day in the life of an Optimizely Developer - Optimizely CMS 12: The advantages and considerations when exploring an upgrade

GRAHAM CARR - LEAD .NET DEVELOPER, 28 Nov 2023 In 2022, Optimizely released CMS 12 as part of its ongoing evolution of the platform to help provide...

Graham Carr | Nov 28, 2023