Episerver is committed to help you come back stronger. Learn more about our COVID-19 response.

All customer success stories Content Cloud customers Commerce Cloud customers Financial services B2B manufacturing B2B distribution B2C retail Commerce Cloud Content Cloud Content Recommendations Content Intelligence AI Personalization Cloud services All capabilities Financial services B2B manufacturing B2B distribution B2C retail Resource library Customer Hub Trust Center Content management Ecommerce Personalization Email marketing CCPA Digital Experience videos Articles Guides Reports & Studies Events Webinars Customer success stories Partner Network App Marketplace Training & Certification Support Expert Services Managed Services Customer Hub User Guide Tips and tricks Developer documentation Quick start for developers Developer community

Headless CMS API Episerver's headless API allows you to use our enterprise CMS platform as coupled, decoupled, and headless architecture. You can easily control and edit content for all your applications in one place.

Hybrid headless architecture gives you the best of headless CMS and traditional CMS

Episerver can serve as the central content hub for your organization, providing a single-source for content across the entire array of your digital properties.

Our hybrid approach gives our customers and developers the best of both headless and traditional CMS. You get the capabilities of headless CMS and you can use features from our enterprise platform, such as personalization, scheduling and projects. You can also build and deliver the experience using Javascript libraries, like Angular and React.

How headless CMS works

With a traditional CMS, the CMS controls how the content is presented. The "head" is responsible for generating the HTML that is parsed and rendered by the browser. A headless CMS, on the other hand, is back-end only. It acts as a content repository that makes content accessible through REST APIs for display on multiple devices.

The headless CMS does not know how content is presented. It is a specialized database, serving content that is transformed into HTML by other systems.

Examples of when a headless approach is useful:

  • To provide content for native applications that are not HTML-based.
  • To integrate with a Point of Sales (POS) network, linking different output systems.
  • To manage content for legacy platforms inside Episerver.

How Episerver's headless CMS works

Episerver's headless API lets you pull content directly from the CMS, bypassing the presentation stack when necessary. Our REST API uses our enterprise search solution, Search & Navigation, to provide an easy way for developers to use the content and not just get items by ID.

With the user interface separated from the application logic, you're free to choose the tools, frameworks and technologies necessary to provide the best possible customer experience in every channel.

The Essential Guide to Decoupled and Headless CMS

Deane Barker, Senior Product Strategy Director at Episerver, defines decoupled and headless CMS and explains some of the technical details and scenarios of how Episerver can work seamlessly as a headless CMS.

Download report

Episerver uses cookies and browser technologies for analytics, personalized content and ads.