Migrating from v2

Voice Monkey v3 is a ground-up rewrite of the platform. Your account, your Alexa skill link, and any paid subscription all carry across to v3 … there are some big differences in how Voice Monkey devices are created.

You’ll need to re-create your Alexa routines and likely update external integrations such as IFTTT..

Will v2 be deprecated?

v2 will keep running at console.voicemonkey.io and the legacy API at api-v2.voicemonkey.io will continue to work. A final end date has not been decided yet but it’s expected that v2 will be deprecated by September 2026.

Am I a v2 User?

If you signed up for Voice Monkey before 27th April 2026, you’re a v2 user. You should continue to access the console at console.voicemonkey.io.

Access to v3 is currently invitation-only - you’ll get an email when your account is ready to move over.

Once you can sign in to v3, this guide tells you what to do next.

What carries over automatically

You don’t have to do anything for these, they already work in v3 as soon as you sign in:

• Your account. Same Amazon login, same email, same name.
• Your subscription. You can stay your existing plan, or switch to a current plan when you want the new features.
• The Alexa skill link. The Voice Monkey Alexa skill stays enabled. You don’t need to disable and re-enable it.
• Your existing v2 setup. Everything in your v2 set-up will keep working when you migrate until you manually switch it off or it’s eventually deprecated.

What’s Changing?

This is an overview of the main differences between v2 and v3…

v2	v3
Voice Monkey Devices were virtual doorbells in Alexa	v3 now uses one generic device
Each speaker or routine trigger was an individual doorbell device, meaning multiple devices in the Alexa app	All speakers and routine triggers appear under one device in the Alexa app
API URL was on host api-v2.voicemonkey.io	Host is now api-v3.voicemonkey.io (API)
API Endpoints were /announcement, /trigger, /flows	Endpoints are now: /announce, /trigger, /flow, /devices
Flows interface used a tree like structure	Flows - is now a visual drag and drop node editor
Flows - HTTP Node did not allow the response to be used	v3 allows you to use the response from a HTTP call in announcements and variables
Schedules were unreliable	Schedules now work far more reliably
API token was one token which could be rotated	v3 allows multiple tokens to be created (Authentication)
IFTTT	You will be required to re-connect Voice Monkey to IFTTT and update your applets with your new v3 devices

Step-by-step migration

Work through this list once your account is invited. It’s recommended you migrate fully and then delete and remove all previous v2 devices from the Voice Monkey console and if necessary from the Alexa app.

1. Sign in to v3 and finish setup

Go to app.voicemonkey.io and sign in with your usual Amazon account. Confirm the set-up details and continue.

2. Import or Re-create your devices

This is the main step every user has to do.

Previously, v2 device = one virtual doorbell device in the Alexa app.

In v3, one device is created called “Alexa Voice Monkey v3” - all speakers and routine triggers will appear under this device when creating an Alexa routine.

Here are the steps you need to follow:

1. Import your devices, or create new ones.
2. Update each of your Alexa routines by updating the trigger (When this happens) device.

The full walkthrough for adding a new device is here.

Naming tip

You don’t have to keep the same names you used in v2. Pick names that make the new device obvious - Living Room Speaker and Front Door Routine will save you confusion later when you wire flows together.

3. Test each new device

Every device has a Test button. Click it and Voice Monkey sends a sample announcement (Speakers) or fires the routine (Routine Triggers). If a test passes, the v3 → Alexa wiring is good. If it doesn’t, see Troubleshooting.

4. Update your API integrations

For each integration that calls the v2 API today (e.g. Home Assistant, custom script etc), you’ll need to now use the v3 host:

1. Open app.voicemonkey.io/tokens , create and copy a v3 token.
2. Open the API Playground - pick the action you want, fill in the device, click Run, and you can use the ready-made snippet from the language tab matching your integration or just the plain URL.
3. Use it in your integration and Test.
4. Move to the next integration.

Highlights of what’s different vs v2:

• Hostname: api-v2.voicemonkey.io → api-v3.voicemonkey.io.
• Auth: the token is the same GET query-string, POST param or Authorization: Bearer
• Announcement endpoint: /announcement → /announce. The TTS field is now speech (was text).

See more at API reference.

5. Update IFTTT applets

If you use IFTTT:

To get it working with v3 you need to re-link/re-connect IFTTT with Voice Monkey, by going to Voice Monkey settings. Open each applet that uses Voice Monkey, sign in to Voice Monkey again with a v3 token, and the existing applet starts routing to your v3 account transparently. The Voice Monkey IFTTT service detects v3 tokens and proxies the action to the v3 API automatically.

6. Import or Re-create Flows

Import your old flows, they are not guaranteed to work. Open Flows → Create Flow.

7. (Optional) Switch to a current plan

Legacy Pro and Legacy Premium are soft-frozen — they keep working at the price you signed up for, but they don’t get future features added. If you want any of the newer feature flags (e.g. media library, premium Flow nodes, AI), pick a current plan from pricing and switch in the Billing section of the console. Paddle handles the proration.

You don’t have to switch. Staying on Legacy Pro / Legacy Premium is a fully supported choice for as long as you want.

When can I turn v2 off?

You don’t need to, and we won’t force a deadline on you. Voice Monkey v2 will keep running for the foreseeable future.

When you feel done — every integration moved, every Echo wired to a v3 device, every API call hitting api-v3 — sign in to console.voicemonkey.io and disable the routines you no longer need. There’s nothing else to do; v2 doesn’t need to be deactivated explicitly.

Common gotchas

A short list of things that catch people out:

• My API call works but says “Device not found”. You’re hitting v3 with a v2 device name (device=living-room). Use the v3 device ID from app.voicemonkey.io/speakers instead.
• My token returns 401. v2 tokens don’t work against api-v3.voicemonkey.io, and v3 tokens don’t work against api-v2.voicemonkey.io. Make sure each integration is using the right token for the host it’s calling.
• My v2 IFTTT applet stopped firing. Check the Voice Monkey IFTTT connection itself isn’t disconnected — IFTTT sometimes drops the authentication so you will have to re-link the app.

If you hit something not on this list, see Troubleshooting or contact support from the help page.

Where next

• Add a device — full walk-through for creating a Speaker or Routine Trigger in v3.
• API overview — the v3 API surface in one page.
• API Playground — generate ready-to-paste snippets for any v3 endpoint.
• Flows — the visual node editor that replaces multi-Routine workarounds.
• Troubleshooting — common issues, fastest fixes.