Good catch @vctr 
I can confirm this as well. I’m always forced to remove those newlines as well.
This is a show-stopper issue for anyone trying to leverage the API to get or update CMS Items. I’d go as far as saying it makes the API near-useless for many CMS related use cases.
Certainly most sites using CMS Collections are also using Rich Text fields, and those Rich Text fields support Code Embeds. If the Code Embeds are stripped out by the API then it makes the CMS endpoints unreliable, there is no data consistency and no trust.
The same issue occurs when trying to export CMS content from Webflow. Code Embeds are stripped from the exported content as well, so this issue appears to be platform-wide. Is now fixed, see here.
I absolutely appreciate the hard work that went into the recent Data API v2 release, but please, pretty please… move this to the top of the roadmap. Bring data consistency to the CMS endpoints. 
@webdev Excellent and timely news! Glad to hear this issue is resolved for CMS import/export. Any word if there are any plans to port this functionality to the CMS API as well?
@nlenkowski - I am not privy to internal queues or timelines. I would suggest you test to see if this is still an issue. I built some environments I used for testing in the past but won’t have a chance to spin them back up and test for a while. Let us know what you find out.
The API does not support this yet, but it is planned. No timeline to share, but we do recognize the gap in features between the in-app features and the API.
1 Like