Is Headless Episerver only available on the DXC?

Vote:
 

Hey there, 

We found the article https://www.episerver.com/products/features/all-features/headless-api/

Will this be only for the DXC? Or can any Episerver customer use this feature? 

#187633
Jan 30, 2018 13:12
Vote:
 

Any customer can use these APIs as long as they're using Episerver Find. This is included in subscriptions to the Digital Exeperience Cloud service.

#187668
Jan 31, 2018 11:08
Vote:
 

David, I seem to remember Mark Hall saying that Find is only required in the initial release of Headless, and that you guys are working on letting certain API calls work with Headless without requiring Find. Can you verify?

#187768
Edited, Feb 02, 2018 9:38
Vote:
 

I also saw this piece of news about the headless API but it doesn't exactly say if it's released or not and I cannot find any documentation about it anywhere either. The lacking documentation is still such an annoyance when working with Episerver...

Does anyone know if there is more information about this somewhere? I'm currently involved in two projects/POCs where we implement our own content APIs based on EpiServer so it would be really useful to know what's around the corner with regards to this.

#187865
Feb 05, 2018 11:33
Vote:
 

Arild, There are multiple packages, main one is Headless Basic (doesn't require Find) allowing you to get content by ID. Search and sorting features uses a package that requires Find.

Emil, Can you contact me at david . bowen at episerver.com and we can get some details to you.

#187880
Feb 05, 2018 13:58
Vote:
 

Hi @david, thanks so much for the info. I am also interested in these packages. The one that doesn't require find - is it available on nuget? And is there documentation? I am tom.dane at bglgroup.co.uk if you want to send anything

#187881
Feb 05, 2018 14:09
Vote:
 

@david what packages are you talking about? Is there any documentation towards tech about these features? This would be nice to have since we tend to get many cases were you have headless up against traditional 

#187882
Feb 05, 2018 14:10
Vote:
 

We're still in our private beta program for this API. We can share some further information directly if you're planning to evaluate or use this API right now. @Eric we'll reach out as well.

#187883
Feb 05, 2018 14:49
Vote:
 

@David: I've exposed parts of the Episerver site content through APIs in several projects over the years; this kind of functionality is and has been often requested. If Episerver now is working on some more standardized way to do this, it would be perfect! Could you give us some pointers as to what this Headless API will contain?

#188336
Feb 20, 2018 11:24
Vote:
 

Hey Anders

(a different David replying here!) In short anything that exposes IContent can be exposed by the API in a listable, searchable way and content can also be accessed by id. Also if a content item has a content area in it then you can ask the API to populate the content area rather than requesting each content item separately. The API is RESTful and also respects visitor groups (if passed in).

Documentation will explain everything I have touched on above! The API itself will be a set of Nuget packages.

David

#188339
Feb 20, 2018 12:26
Vote:
 

This sounds relevant for what we're doing. When will this be available and where can we read more about it? It's a bit hard to understand why Episerver as a company are talking about a feature like this and then hold back relevant information. It's not exactly helping...

I'm involved in several projects where we're building similar stuff ourselves on top of Epi and are about to commit to a long-term solution based on what we've done so far. It would be very helpful to know if these features are worth waiting for or if we should continue building on what we have.

/Emil

#188354
Feb 20, 2018 17:42
Vote:
 
#189264
Mar 14, 2018 11:17
Vote:
 

Asked for it yesterday evening by Marcus Hoffman and here it is :) Nice work. Had a session about your headless api for a customer and nice to be able to show them in such a short notice. 

#189281
Mar 14, 2018 13:59
Vote:
 
#189299
Mar 14, 2018 18:06
Vote:
 

For information the content delivery API does not require Digital Experience Cloud Service. It does need Episerver Find for search capabilities. 

#189300
Mar 14, 2018 18:08
Vote:
 

Thanks for sharing :)!

#190890
Apr 18, 2018 12:59
Vote:
 

No worries David, always happy to help!

Below is a new post with some more details, 

http://sunnyjhunjhunwala.com/blog/episerver-headless-content-api-reactjs

#191075
Edited, Apr 19, 2018 18:07