November Happy Hour will be moved to Thursday December 5th.
AI OnAI Off
Content Delivery API -- Not returning all properties of Page
Hi Dileep, I'm assuming you are making a call to the content delivery API with url something like this: /api/episerver/v2.0/content/5?
By the looks of the response, you have fetched content by id 5 and that is a system folder for Episerver Forms in that environment. What is it you are trying to fetch from the API?
You have to note that content IDs are not the same in all environments. So if you for example want the site start page, look what is the id of the start page (site start page) in Episerver edit mode (hover your cursor over the start page to see the id of the page) or from Admin view (site configuration, what is configured as the site start page) - and then use that id in your call.
Edited,
Mar 22, 2020 11:23
Dileep D
- Mar 23, 2020 0:33
Thanks for pointing out. Feels so stupid of me now :). Should have taken time investigating this before posting the question.
All the environments had start page id as 5 other than the one I was looking for. It was 6 here. For some reason my web app started throwing error ( is currently unable to handle this request.HTTP ERROR 500) before I could test it out.
I will test it once this issue is resolved and accept your answer.
All the environments had start page id as 5 other than the one I was looking for. It was 6 here. For some reason my web app started throwing error ( is currently unable to handle this request.HTTP ERROR 500) before I could test it out.
I will test it once this issue is resolved and accept your answer.
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
I had implemented Content Delivery API which seems to be working fine in local environment. After I push it to DXC and had ensured that I gave read access to contentapiread to root and to all sub pages (Apply settings for all subitems).
When I hit the API I get the response but it has only the base ContentAPI model response. It doesn't have any of the properties of the page. Below is the sample.
Response: