<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/585a0ad209514df18937ce48607b6b25&quot; frameborder=&quot;0&quot; width=&quot;2258&quot; height=&quot;1693&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1693</height><width>2258</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1693</thumbnail_height><thumbnail_width>2258</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/585a0ad209514df18937ce48607b6b25-1666644994365.gif</thumbnail_url><duration>4804.82</duration><title>Floppy and API Calls/API Objects in Bubble</title><description>A long and rambling live Bubbling session where I answer a question from forum user @future about &quot;can floppy store the results of an API call&quot;? The answer is &quot;yes and no&quot;. While we CAN in fact store the raw body response from an API call, we cannot store the API call object itself. I show why this is and I show the (slightly complicated to explain, but ultimately rather simple) way that we can recover (or &quot;rehydrate&quot;) an API call object from the raw JSON body. Also, I talk about potential alternatives to fetching and storing raw body responses and talk about some of the data type issues that are involved.</description></oembed>