Manual / Migration

Parallel phase with webhooks

Updated on 2026-04-26

What is the parallel phase?

Between your migration and your definitive switch we recommend a 2-4 week parallel phase: MyTourist remains your primary system, BedFlow runs as a shadow with the same data. New bookings coming into MT also appear in BedFlow in real-time.

Advantage: you can test BedFlow with live data without risk — if something does not work, you still have MT. Only when you are 100% comfortable do you put BedFlow live for good.

How does it work technically?

An API key alone is not enough for live sync. An API key lets us read your MT data — once or on demand — but MT does not call us when something changes. For that you need webhooks.

A webhook is a URL that you configure in MyTourist. On every event (new booking, payment, check-in, invoice) MT sends a POST request to that URL. We receive it and immediately update your BedFlow data.

Step 1 — Find your unique webhook URL

After the migration you see, at step 6 of the wizard, a unique URL for your property, e.g.:

https://bedflow.eu/webhooks/mytourist/aB3kP9xQ2mL7nR5tY8wE1zU4vH6cI0sD9fG2jK4o

The long string at the end is a token that ensures only your MT account can write to your BedFlow property. Click the Copy button — you need this URL straight away in MyTourist.

💡 Lost? Open your BedFlow admin → Properties → your property → field Webhook URL.

Step 2 — Paste into MyTourist

In MyTourist:

  1. Settings → Webhooks
  2. Click + Add webhook
  3. URL: paste your BedFlow webhook URL
  4. Events — tick all of the following:
    • booking.created
    • booking.updated
    • booking.cancelled
    • booking.checkin
    • booking.checkout
    • invoice.created
    • invoice.paid
    • invoice.cancelled
    • payment.received
  5. Status: active
  6. Click Save.

Step 3 — Test

In MyTourist: create a test booking (e.g. for yourself, 1 night, today→tomorrow). Wait 5 seconds, then go to your BedFlow admin → Bookings. The booking should be there.

Not visible? Check:

  • In MT → Webhooks → your webhook → tab Logs — do you see a 200 response from bedflow.eu?
  • No 200? Give support a ticket reply (free, because it is not a question but a possible bug in our webhook handler).

What does BedFlow do with the events?

| MT event | BedFlow action | |---|---| | booking.created | Create new booking, match debtor, update calendar | | booking.updated | Update existing booking, sync price/date | | booking.cancelled | Status → cancelled, room available again | | booking.checkin/out | Update status, trigger housekeeping task | | invoice.created | Invoice in BedFlow with PDF download | | invoice.paid | Status → paid, register payment | | payment.received | Payment log in financial tab |

Switch-over: from parallel to fully BedFlow

When you decide to go 100% across:

  1. Switch your booking widget on your website to the BedFlow widget URL.
  2. Remove the webhook in MyTourist (settings → webhooks → delete).
  3. Set MyTourist to read-only mode or cancel the subscription.
  4. BedFlow now becomes the single source.

We recommend keeping MT for 30 days as a safety net, but that is your choice.

Doubts or issues?

  • Webhook does not work → bug ticket, free fix
  • Not sure how to configure → book 30 min screen-share (€45)
  • Want help to switch → support@bedflow.eu
← Back to category