Explore the Demo Application

The Vonage Video API lets you spin up a room and invite participants in minutes. Before wiring anything together, you can explore the existing demos and understand what the code is doing behind the scenes.

See the Demo

If you want to see the experience before you touch any code, use the public demo stack. All of the pieces are open source so you can re-use the exact setup once you are ready to customize it.

Launch the Node.js Server

The sample experience relies on a backend server to mint session tokens and coordinate users. You can deploy the Vonage Video Learning Server straight from Code Hub:

  1. Visit the Vonage Video Learning Server (Node.js) template in Code Hub.
  2. Select Get code → Create a new development environment and name it something like Vonage Video Demo.
  3. Assign (or purchase) a Vonage phone number when prompted so the workspace can handle SIP calls in future demos.
  4. After Code Hub provisions the workspace, open the built-in terminal and run vcr deploy.
  5. Record the instance host address from the deployment output—you will need it for the front-end sample.

Code Hub generates the Vonage Application, its keys, and the environment configuration automatically. You can browse or edit the code directly in the online VS Code environment while it runs in the background.

Test the Front End

The multiparty demo frontend lives at Vonage-Community/video-api-web-samples → Archiving. The easiest way to run it is to click Open in StackBlitz in the README.

Once StackBlitz loads:

  1. Open js/config.js.
  2. Set SAMPLE_SERVER_BASE_URL to the instance host address from the learning server deployment.
  3. Save the file and reload the preview pane. Grant microphone/camera access when prompted.

You should see your own feed in the layout. Share the StackBlitz URL with another device or colleague to verify that multiple people can join the session, publish video, and view each other.

StackBlitz also exposes the full source tree, so you can trace exactly how the client connects to your backend and how archiving is triggered.