I did play around with this because it felt like something was up. Here I just have a GET request for Calendly events, but the raw body text is empty (and also empty if filtered/taking first item:format as text(This event type’s raw body text))
Is this really expected behaviour? I was under the impression that raw body text would just be the raw JSON response of the API request… if this is supposed to be empty then I wonder what raw body text means. Learn something new every day…
Hi @georgecollier,
look at this thread, it might interest you 
Yes that’s how :format as text works.
Are you implying the response data has a variable and potentially large number of keys? If so, I agree this is not a useful solution. Even the initializing of the response structure into fields would be problematic, as Bubble will only parse values for keys baked into the initialized structure.
One solution not yet discussed here is changing the API Connector response body type to raw text, i.e. turn off Bubble’s property parsing, and do it yourself in code with JSON.parse(text). The big downside is losing the useful properties for dynamic data, for which some people in the forum have come up with sending the data back into an API endpoint for the parsing. I think you don’t need this level of complexity.
If the purpose is just to display the additional data, relying on the “unreleased feature” of the raw body text sounds more reasonable (if you can get it to work).
I’d do the list filter inside the JS code …
Yes.
Yep, this is what I have done at the end 
Thanks @mishav for your support!!
If I hear about another simpler way to do it, will let you know! 
