Webex for Developers Newsletter – November 2025
November 6, 2025
Greetings, Webex developers! Check out all the latest updates, events, and community announcements for the entire Webex Developer ecosystem right here.
📺 Public Developer Webinar: Introducing Webex Bring Your Own Virtual Agent (BYOVA)
On Wednesday, November 12th at 1:00PM EST, join this public webinar to explore the new Bring Your Own Virtual Agent (BYOVA) capability from Webex, enabling developers to integrate any voice-based virtual AI agent with Webex Contact Center. This session will provide an overview of the BYOVA feature, discuss a range of practical use cases, and deliver a step-by-step walkthrough of configuring and connecting to a virtual agent—featuring AWS Lex as an example. Discover how BYOVA empowers you to deliver customized, intelligent voice experiences for your customers, regardless of your AI platform of choice. Live Q&A included!
If you can’t make it to the live session, no problem! You can watch all our previous webinar recordings on-demand, including the most recent one, Mastering Webex API Troubleshooting - Your Essential Guide to Building Successful Integrations,, right on our webinars page. Come and explore our growing library!
📫 Announcing The Official Webex Postman Workspace
Tired of juggling API docs and one-off tests? In a recent blog post by Technical Leader for Webex Developer Relations, Adam Weeks, discover how the official Webex Postman Workspace can streamline your workflow, from authentication to complex API sequences with a set of Postman collections. This curated collection resources is a game-changer for anyone building with Webex. It’s more than just a list of endpoints; it’s a complete development environment that can significantly streamline your workflow.
👩🏽🔧 Why Every Webex Developer Needs This Troubleshooting Guide
Ever found yourself staring blankly at a HTTP 500 error or scratching your head over an SDK that just won't behave? You're not alone. When developing with the Webex APIs and SDKs, encountering technical issues is sometimes inevitable. In this blog post, Developer Support Engineer, Mike Palkovich, walks us through the recently published Webex API Troubleshooting Guide to show us some best practices for resolving common developer issues that may arise.
🎪 WebexOne 2025 Developer Recap: Building the Future of Collaboration
The WebexOne 2025 event was filled with many exciting moments, and we’re eager to share some of the standouts for our developer community. Held in San Diego, CA from September 28 to October 1, this year’s occasion provided a fantastic opportunity for developers and other technology enthusiasts to connect, learn, and exchange ideas. To see what went on, check out this new blog post by the Leader of Developer Evangelism, Phil Bellanti, for a full recap of all the developer sessions and activities that took place.
📝 Webex API Recent Changelog Hits
Highlighting some important updates recently listed in the Webex API Changelogs:
BREAKING CHANGE IN WEBEX CONTACT CENTER APIs – October 13, 2025:
New APIs to manage Resource Collections have been added.
Version 3 APIs for managing User Profiles have been added:
- Bulk export User Profiles
- Bulk save User Profiles
- Create a new User Profile
- Delete specific User Profile by ID
- Get specific User Profile by ID
- List user profiles
- Update specific User Profile by ID
Effective Access control list based on User profile permissions and associated resource collections can now be fetched with this new API - Get specific User Profile ACL by ID.
The following User Profile APIs have been deprecated and will be removed soon - Bulk export User Profiles(Version 1). Older Version 1 of User Profile APIs have been removed as they are non-functional and no longer relevant: Bulk save User Profiles, Delete specific User Profile by ID, Get specific User Profile by ID, List user profiles, and Update specific User Profile by ID.
Full Webex Contact Center API Changelog →
UPDATE FOR THE WEBEX APIs – October 21, 2025:
A new field internal is added in Wholesale Billing Reports POST API. This is not a mandatory parameter and maintains backward compatibility.