> For the complete documentation index, see [llms.txt](https://docs.partner.aboutyou.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.partner.aboutyou.com/webinar-library/recordings.md). # Recordings Welcome to our Webinar Recording Library. This space provides access to recordings of our past webinars and online sessions, giving you the opportunity to revisit important topics. Our webinars cover a wide range of topics, including product and platform updates, new features and functionalities, marketplace processes, best practices, and important announcements. Each session is designed to provide practical insights and guidance to help you get the most out of our platform and services. ​You can watch the recordings at your convenience and return to them whenever you need a refresher on a specific topic. Where available, you will also find additional resources and documentation related to the webinar. We regularly add new recordings to this space, so check back for the latest sessions and updates. *** #### Webinar: Mastering Product Creation We unveiled our brand-new Bulk Product Uploads feature and provided a step-by-step guide to creating and enriching your products. We also answered some of our partners’ questions during the session. {% embed url="" %} ​Hosted: 11.08.2026 *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.partner.aboutyou.com/webinar-library/recordings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.