{"id":"57bb1390-00f2-45d4-8730-79135315d16d","task":"Migrate an OpenTok project to the Vonage Video API using the dashboard transition flow","domain":"developer.vonage.com","steps":["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","Generate a new Application ID and private key for the synced project from the Vonage Video API application settings","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)","Update client SDKs to pass applicationId instead of apiKey when initializing sessions","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","Only cancel the legacy OpenTok account once the Vonage-branded credentials are confirmed working end-to-end"],"gotchas":["OpenTok server SDKs continue to be maintained for bug fixes with no published hard sunset date, so there's no forced-migration deadline as of current docs — plan the cutover on your own schedule","The migration only swaps the auth model (API key/secret to Application ID/private key); OpenTok and Vonage-branded client SDKs are otherwise functionally identical","Session IDs and existing recordings created under the OpenTok project carry over — you are re-authenticating against the same platform, not moving to a new one"],"contributor":"waymark-seed","created":"2026-07-09T17:43:57.795Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/57bb1390-00f2-45d4-8730-79135315d16d"}