Routy

What to expect when you move to the new Routy

Last updated: October 2026

We're moving your account from legacy Routy to the new Routy. Your existing tracking links are already migrated and they don't change. The one change on your side is the API base URL.

Your tracking links are already migrated and don't change

Every tracking link you created in legacy Routy is already in the new Routy, with the same domain, the same link and the same parameters. You don't edit them, re-issue them, re-create them, or ask anyone to swap them out.

  • Your old links are already on the new platform. Nothing was left behind in legacy Routy.
  • Links you have placed in ads, emails, apps and sites keep running, including the ones sitting somewhere you can no longer edit.
  • Your traffic sources and your partners keep using the links you gave them. There's nothing to send them.
  • Postbacks and pixels fire to the same URLs, with the same parameters.
  • Clicks and conversions arriving through those links show up in the new Routy from the cutover onwards.

Your new Routy account is ready

Log in and look around. Don't add new accounts, links or traffic sources yet. Your data comes across in the final migration on cutover day, and anything you create before then can clash with it.

What stays the same

You don't need to change any of the following.

  • Your tracking links, postbacks and pixels stay as they are. They are already migrated.
  • Your API integration keeps working. The new Routy runs a copy of the legacy Routy API, the backward-compatible API, so your existing calls behave the same way.
  • Your current API key works with the backward-compatible API.

The one change: your API base URL

Point your API calls to the new base URL. This is the only edit on your side, and it does not touch your tracking links. The path after the base stays the same, so a call that went to https://public-api.routy.app/accounts now goes to https://platform.routy.app/api/accounts.

  • Legacy Routy base URL: https://public-api.routy.app/
  • New Routy base URL: https://platform.routy.app/api/

Optional: the modern API

The new Routy is API-first, and its modern API has additional capabilities. It runs on the same host as the backward-compatible API, under /api/v1/, so what separates the two is the path and the key rather than the server.

  • Modern API base URL: https://platform.routy.app/api/v1/

To use it, generate a new API key. If you stay on the backward-compatible API, your setup keeps working as it is.

The two APIs use separate keys. Your current API key works only with the backward-compatible API, and a key you generate for the modern API works only with the modern API.

Each API publishes an OpenAPI document you can read or generate a client from. The backward-compatible API is at https://platform.routy.app/api/swagger/legacy/swagger.json and the modern API is at https://platform.routy.app/api/swagger/v1/swagger.json.

How cutover day runs

The cutover happens at a time you pick on migration day, for example midday.

  1. At that time, you stop working in legacy Routy and start working in the new Routy.
  2. We run a final data migration from legacy Routy to the new Routy, which takes about 30 minutes.
  3. Once it finishes, you're fully live on the new Routy.

What we need from you

  1. Confirm your API calls work against the new base URL, so your integration is ready for the cutover.
  2. Tell us which time of day suits you for the cutover.

There's nothing to do about your tracking links.