Hi Voicemod team, I’d like to bring up an issue that’s causing confusion and frustration for both users and third-party developers. Right now, Voicemod V3 lacks proper public API support, which is breaking integrations that many users rely on. The Stream Deck Integration Is Not Using the Public API It’s been said that "Stream Deck works fine with V3," which is true—but that’s because it does not use the public API. Instead, it communicates via a local WebSocket connection using commands like: Voicemod.sendMessageToServer('getVoices') However, third-party apps are expected to use Voicemod’s Control API, which is REST-based and requires authentication tokens. Unfortunately, this API does not provide the same level of functionality, meaning third-party apps simply can’t replicate what Stream Deck is doing. This Creates Confusion for Users Many users download Voicemod expecting their favorite integrations to work, only to find that they don’t. Since Voicemod does not clearly communicate the API limitations, users assume the issue is on the third-party app’s side. This results in: Users complaining in third-party support channels about Voicemod V3 breaking their integrations. Developers having to explain that this is not their fault—but rather a missing feature in Voicemod. A back-and-forth blame game that could be avoided with clearer communication. The Download Page Does Not Offer a Choice Currently, when users go to download Voicemod, there is no selection menu for different versions—V3 is simply forced upon them. In some rare cases, users see a link to V2 after the download has already started, but this is inconsistent. Since V3 is not fully API-ready, shouldn’t V2 remain easily available for those who need full integration support? A simple version selection on the download page would make this much clearer. Suggested Solutions To resolve these issues, the best approach would be: ✅ Provide a clear, accessible way to download V2 until V3 has full API support. ✅ Officially document the local WebSocket API (or allow third-party developers access to it, just like Stream Deck). ✅ Improve communication with users so they understand which integrations work with V3 and which require V2. This isn’t just about third-party apps needing an API—it’s about avoiding unnecessary confusion for users and ensuring Voicemod remains a great experience for everyone. Would love to hear your thoughts on this!
