<?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/db4257701e514ee6a6fbac3eabd3cf7d&quot; frameborder=&quot;0&quot; width=&quot;1668&quot; height=&quot;1251&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1251</height><width>1668</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1251</thumbnail_height><thumbnail_width>1668</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/db4257701e514ee6a6fbac3eabd3cf7d-77bed855cb84a531.gif</thumbnail_url><duration>257.966</duration><title>Auth and Product Authorization Issues</title><description>This Loom discusses API authorization and product and department management behaviors. The presenter attempts to send a Gson payload to authenticate and retrieve products tied to a specific department, noting errors such as Unauthorized, Invalid or missing products, and Department not found. They describe an update flow where a product is updated and later marked invalid and mention cases where a product is not present in the department. They also confirm they cannot delete and that certain actions like creating a product require proper authentication with an authorized username.</description></oembed>