Umbraco Heartcore - FAQ

Well first and foremost, Umbraco Heartcore is a content management system that is easy and intuitive to use.

But it's loved by both developers and content editors because it does a lot more for usability than being just a data management tool.

The surrounding services like media library, image service, CDN and content delivery platform add a lot to the complete package - to create the well-rounded service that you get with Umbraco Heartcore.

Heartcore is built on the experience and feedback that comes from Umbraco's long history as an open source CMS.

This experience has led us to create a friendly backend and flexible editing experience - loved by both developers and content editors. 

With Heartcore we truly put the Management in Content Management System while also providing you with the features you need to distribute your content across websites, apps, screens and devices.

See details and features for each pricing plan on our Heartcore pricing page.

The answer is that Heartcore is more than just a headless CMS. It's a managed platform that adds a lot of extra functionality on top of the CMS to help developers and editors deliver delightful digital experiences to your users:

• An updated and secure Backoffice, so you don't have to spend time on patches and security fixes
• API managed by us so you don't have yet another codebase to worry about
• Hosting and CDN is included to provide you with a secure place for your content that guarantees low latency when displayed worldwide
• GraphQL and Preview API already included, to ensure high performance in your solution and give your editors an even greater experience. 

You can essentially use anything that supports HTTP, which means most! We have extensive API Documentation, so it should be easy to get started.

In terms of Client Libraries, we have a .NET Core and a NodeJS library available making it extra easy to get started with these two programming languages (C# and Javascript).

Yes! This is possible with webhooks. You can setup webhooks for Save, Delete and Publish events and you can filter by Document Types to trigger events for Content of a specific type. See the Umbraco Heartcore documentation for more information.

Published Content is exposed via the Content Delivery API and is public by default. It is easy to set up the Content Delivery API to require authentication through the Umbraco Backoffice in the “Headless” section.

When Creating, Updating, Deleting things like Content and Media you use the Content Management API, which is protected by default. See the Umbraco Heartcore documentation for more information.

You can authenticate using oAuth or an API-Key.

API Keys are created through the backoffice, and many keys can be created for each user. You can choose to set an expiration date for the API Keys you create or create keys that live forever - and an API Key can always be revoked.

Read more about how to do this in the API documentation for Umbraco Heartcore.

Custom code is not currently available with Umbraco Heartcore, but we're keeping an open mind. 

Have a suggestion or some ideas about this? Please let us know!

Unfortunately, this isn't a possibility on our Cloud platforms. However, our development team are working hard on some super authentication improvements, which will in turn open up new possibilities.

You can read more about this on the blog and keep tabs on releases on our product roadmap.