<?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/717260c99d834fccbb894a71b2a88630&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/717260c99d834fccbb894a71b2a88630-ee66bc7f9934c755.gif</thumbnail_url><duration>107.9613</duration><title>API Call Troubleshooting</title><description>In this video, I&apos;m walking you through my attempts to trigger a call using the API. I successfully tested the initial requests, but I&apos;m encountering a persistent 400 error when trying to send an HTTP request. I’ve included the details of my setup and the authentication process, which seems to be in order. I would appreciate your insights on resolving this issue, especially regarding the assistant ID.</description></oembed>