Manual / Migration

Generating an API key in MyTourist

Updated on 2026-10-01

Goal

You need an API key + base URL to read your MyTourist data through our migration wizard. The key only grants read access — we don't change anything in your MyTourist.

Step 1 — Log in to MyTourist

Go to app.mytourist.cloud and log in as the administrator of your property.

Step 2 — Navigate to Plugins → API

In the main menu on the left: Plugins → API. If you don't see the menu item, contact your MyTourist account manager (your role may not have API access).

Step 3 — Generate a new key

Click + New API key.

  • Name: type BedFlow migration — handy for finding it again later.
  • Permissions: tick read-only access for:
    • bookings
    • debtors
    • invoices
    • roomtypes
    • products
    • vouchers
    • calendar
  • Write access: leave everything off. We don't need it and it is an unnecessary risk.

Click Create.

Step 4 — Copy the key (visible only once!)

MyTourist shows the key only once. Copy it straight away or write it down somewhere safe — if you close this window, you will never see it again and will have to generate a new one.

The key typically looks like this:

mt_live_KX9p7nRm2qLaY8wE1zU4vH6cI0sD9fG2jK4o

Step 5 — The base URL

For most accounts this is:

https://app.mytourist.cloud/api/v1

Only change this if MyTourist has explicitly given you a different address (e.g. enterprise customers on a dedicated subdomain).

The wizard only accepts an https:// address on mytourist.cloud (a subdomain is fine). It refuses any other domain, an IP address or a port number: we never send your key to an address outside MyTourist.

Step 6 — Paste into BedFlow

At bedflow.eu/migrate (step 2 of the wizard), paste both values. Click Next — we test straight away whether the connection works. If there is an error, you get a clear message ("No connection — check your key and URL"); if it succeeds, you continue to the dry-run preview.

Security

  • Keep your key safe: not in a Word document on your desktop, not in your mailbox.
  • One key for BedFlow: create a separate key for BedFlow and don't use the same one as for other integrations. That way you can revoke this one key without affecting your other integrations.
  • What do we do with it? After the import, successful or not, we delete the key from the migration. It remains stored with your property, so that BedFlow can fetch new bookings from MyTourist during the parallel phase.
  • Revoke the key once you switch over completely: delete it in MyTourist as soon as you no longer work in MyTourist. From then on, nobody can use it to read your MyTourist data.

What if I don't have API access?

Some MyTourist packages do not offer API access. Two options:

  1. Ask MyTourist support — for active customers, API access can usually be added at no cost.
  2. Book a free migration call with us. We'll help you request the right access, or you can transfer your reservations with a CSV export: see Importing your existing data.
← Back to category