{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/282145e9dcd0490981fbd8d45030b1a6\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/282145e9dcd0490981fbd8d45030b1a6-422bc39428aa8b45.gif","duration":73.836,"title":"Token Consumption and Preserved Network Log","description":"This Loom explains a token-based flow where clicking a button opens another page and the token is consumed. The speaker notes that they enabled preserve log in the network tools to capture the request to localhost along with a token sourced from the database via a token page. When opening the new window, they observe that the token no longer exists because it has been used. The Loom ends by checking storage after this token consumption."}