json rte serializer like the typescript package

[divinebovine]

Hi,

I'm currently consuming localized content from content stack and in my typescript projects I'm using content stack's json-rte-serializer. In that project, the interface is much simpler, such that I can just pass the json rte object to the jsonToHtml function and get html. However on the dotnet side, it looks like I have to use the ContentstackClient to fetch the data so that I can create an Options object for the RenderContent or JsonToHtml functions.

In my organization, I have to pull content stack data via an internal API, so I can't use the ContentstackClient. Do you have any suggestions on how to work around this?

[cs-raj]

Hey @divinebovine
Thanks for raising this, we will check on our end and get back
cc: @netrajpatel @nadeem-cs

[nadeem-cs]

Thanks for reaching out!

You do not need to use ContentstackClient to work with the .NET JSON RTE utilities. The examples in our docs use ContentstackClient only to demonstrate a common usage pattern, but the utilities themselves do not require the SDK’s client or its fetch workflow.

If your organization fetches Contentstack data through an internal API, that’s completely fine. You can:

Install the Contentstack.Utils package independently, without using the Delivery SDK.

Take the JSON RTE object returned by your internal API.

Pass that object directly to Utils.JsonToHtml() (or Utils.RenderContent()) along with a simple Options instance.

Example:

using Contentstack.Utils;
using Contentstack.Utils.Models;

// 'rteObject' is the RTE JSON you received from your internal API response
var options = new Options(); // Or your custom options
string html = Utils.JsonToHtml(rteObject, options);

As long as your internal API returns the standard Contentstack RTE JSON schema, the serializer will work the same way as it does when using the Delivery SDK.

So yes, you can completely skip using ContentstackClient; just pass your API’s response into the utility functions.

I’m closing this issue for now.
If you need more clarity, feel free to reopen the issue or reach out to us via customer support - we’re happy to help!