This could work. You’ll then need to filter out the entire response to only isolate the actual JSON you want. And if done on a List of things, will need to ensure you’re API call is dynamic in the URL to accept the UID or no UID if wanting to switch between list and single item with just one API call in the API connector. I think the hardest thing is to then filter the response just to get the actual JSON.
And unfortunately, the rumored :parsed as JSON operator is not a Parse as JSON and instead is a Parse FROM JSON feature, so if that does get released, it wouldn’t help in this situation.
@philipp.laengle107 are you using any existing plugin that even client side successfully parses a bubble custom data type ‘thing’ into an actual JSON as it should be, complete with option set fields and related data type fields expressed as they should be (ie: option is display and related field is uid)? If so, please let me know which one.
Are you looking for one that will take a single bubble custom data type with related data type fields and express one single nested JSON that includes the keys and values of the related data type, or is just the unique ID of the related type sufficient?