<?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/ca195c171ccb4c279b4b559bc4785724&quot; frameborder=&quot;0&quot; width=&quot;830&quot; height=&quot;622&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>622</height><width>830</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>622</thumbnail_height><thumbnail_width>830</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/ca195c171ccb4c279b4b559bc4785724-692a07bc6bc40964.gif</thumbnail_url><duration>276.241</duration><title>Creating an API Key in Whippy: A Step-by-Step Guide 🔑</title><description>In this video, I walk you through how to create an API key in WIPI and explain when and why you might need one. API keys are essential for automating tasks like sending messages or syncing data with your CRM or ATS, allowing systems to communicate securely without manual intervention. I demonstrate the process of creating an API key, including naming it and managing its settings. I also emphasize the importance of securely storing your API key and treating it like a password. If you&apos;re only using WIPI through the app, you won’t need an API key, but if you plan to integrate with other systems, this is a crucial step.</description></oembed>