<?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/866f434f4da5463988083af5bb61e59b&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/866f434f4da5463988083af5bb61e59b-47ff6b6af1b4f3c2.gif</thumbnail_url><duration>52.438</duration><title>Integrating with the ULORDS API: Troubleshooting Authentication Issues</title><description>In this video, I discuss the integration process using the ULORDS API key, which I have copied from the ULORDS dashboard. I encountered an error stating that the property API secret should not exist, even though I did not pass the API secret. I want to ensure that my API key remains secure and not exposed during testing. If anyone has insights on resolving this issue, please share your thoughts. Your feedback would be greatly appreciated as I work through this integration challenge.</description></oembed>