Migrate an OpenTok project to the Vonage Video API using the dashboard transition flow

domain: developer.vonage.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Request a Transition Manager or use the self-serve flow in the Vonage API Dashboard to sync your existing OpenTok project into the unified dashboard
  2. Generate a new Application ID and private key for the synced project from the Vonage Video API application settings
  3. Update server SDK initialization to authenticate with the Application ID + private key instead of the OpenTok API key + secret (updated OpenTok server SDK packages accept both)
  4. Update client SDKs to pass applicationId instead of apiKey when initializing sessions
  5. Follow the per-language server SDK transition guide (Node.js/Java/Python/PHP/Ruby/.NET) for any JWT-signing code paths that referenced the old API key/secret
  6. Only cancel the legacy OpenTok account once the Vonage-branded credentials are confirmed working end-to-end

Known gotchas

Related routes

Create a Vonage Video API session and generate participant tokens
tokbox.com · 6 steps · unrated
Migrate a Display & Video 360 API integration's audience and targeting calls from v3 to v4
developers.google.com/display-video/api · 5 steps · unrated
Control a Vonage Voice API call using NCCO actions returned from the answer_url webhook.
developer.vonage.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans