[Request]

Add functionality – either via the existing vMix HTTP API or via a minimal webpage hosted by vMix itself – that allows resetting the password / magic link for a single vMix Call input without needing full access to the vMix UI.

In other words: a lightweight “Guest Link Manager” that can:

• Reset the Call ID/password for a specific existing Video Call input
  
• Generate a fresh “magic link” (e.g. vmixcall.com / advanced.vmixcall.com URL)
  
• Expose this via:
  
  
  
  • an authenticated HTTP API call, and/or
    
  • a very simple, restricted web page on the vMix Web Controller
    
  
  

[Use case]

We have workflows where:

• The technical operator has full access to the vMix machine.
  
• A separate producer/presenter team is responsible for inviting guests and sending vMix Call links.
  
• For security and stability reasons, we do not want to:
  
  
  
  • Give producers remote desktop / full vMix access, or
    
  • Hand out permanent, static vMix Call links that work indefinitely.
    
  
  

Right now, resetting a guest’s vMix Call link generally means:

1. Someone with full vMix access has to open the preset.
   
2. Edit the Video Call input.
   
3. Manually change the password / Call ID.
   
4. Copy the new link and send it to the producer.
   

This doesn’t scale well when you have many guests, multiple shows, or distributed teams, and it encourages unsafe habits like:

• Sharing long-lived links that can be joined at any time.
  
• Sharing screenshots/recordings of the vMix UI just so producers can see the current links.
  

[Desired behaviour]

For an existing vMix Call input:

• Allow the call password / ID to be reset on demand without touching the main vMix interface.
  
• Return or display a ready-to-use join URL, e.g.:
  
  
  Code:

  https://www.vmixcall.com/call.aspx?key=XXXX&Name=Guest
  

  
  or the equivalent advanced.vmixcall.com URL.
  

Two example implementation options (either would already be hugely useful):

1. API endpoint

• New function in the HTTP API, for example:
  
  
  Code:

  Function=ResetCallPassword&Input=<name or number>
  

  
  
• Response could be XML/JSON with:
  
  
  
  • Input name / number
    
  • New password / key
    
  • Full join URL
  
  

This would let us build our own secure “producer portal” that talks to vMix, without exposing the full UI.

2. Restricted web page in the Web Controller

• A simple page (e.g. “Call Links” tab) which:
  
  
  
  • Lists all Video Call inputs
    
  • Shows current status (connected / not connected)
    
  • Has a button to reset the link for that input
    
  • Displays / copies the new URL
    
  
  
• Access could be protected with its own password or role, separate from the full Web Controller / main vMix UI.
  

Why this is important

Security

• Avoids handing out static links that can be reused at any time by anyone who finds them.
  
• Reduces the number of people who need direct access to the vMix machine, RDP, etc.
  
• Better separation of roles: operators run the show; producers manage guests.
  

Operational efficiency

• Producers can self-serve guest links without waiting on a vMix operator.
  
• Makes it easy to issue fresh, short-lived links per show or per segment.
  
• Ideal for recurring productions, multi-location teams, and OB/remote setups.
  

Fits existing vMix strengths

• vMix already exposes a powerful HTTP API and Web Controller; this would be a natural extension of that ecosystem.
  
• Existing presets and Video Call inputs are reused – we don’t need dynamic input creation, only password/link reset for inputs that already exist in the preset.
  

Nice-to-have extras (if feasible)

• Optional parameter for a simple note/label field exposed in the API (e.g. “Show X – Guest 3”).
  
• A read-only API endpoint that lists:
  
  
  
  • All Video Call inputs
    
  • Their current call password / key
    
  • Connection status
    
  
  
• Role/permission separation so a “Producer” role can only see the Call Manager, not the entire Web Controller.
  

In short:

"A way to reset and retrieve a single vMix Call link remotely (API or limited webpage) without giving full access to the vMix interface."

Apologies if this already exists, if so please point me in the right direction.

Many thanks,
Alan