StayTechLink

If your Property is listed on another website that has a SuperControl calendar, you can use our integration to automatically push bookings from your StayTech site to your Supercontrol site.

Step 1: Tell SuperControl

Before you start you must let SuperControl know that you’re setting up a connection with StayTech.

They need to be aware that you’ll be pushing bookings to your Supercontrol account using your Client ID and Property ID. We use a shared API key for this connection, so it’s important that SuperControl has this on record for your property.

Connecting Your Account

  1. Go to Property > Edit > Sync > SuperControl in StayTech admin.
  2. Enter your SuperControl Client ID and Property ID.
  3. Save the details - this will activate the integration.

Once set up:

  • You’ll now see updates and booking pushes through the Notifications area.

How are bookings sent

  • StayTech pushes bookings to SuperControl only.

    Once a booking is pushed, it can not be updated - it’s a one-time export.

Example: If a provisional booking is pushed and later confirmed, we delete the original and re-send it as a confirmed booking.

Any changes made in StayTech after sending will not reflect in SuperControl, so SuperControl should not be used for managing booking changes - only for visibility.

Availability setup

To bring availability from SuperControl into StayTech:

  1. Get the iCal link from SuperControl.
  2. Add it in StayTech under your property's Remote Calendars.
  3. Important: Tick the option that says “Exclude from StayTech Link” *.
  4. Mark the status to 'Automatic'

*This tells the system not to send availability from StayTech back to SuperControl, which avoids duplicating data or creating clashes - since the StayTech → SuperControl push already covers bookings.

Error monitoring

Watch your Notifications for issues:

  • You can filter notifications to show warnings.
  • Then login to SuperControl and Verify that the bookings are showing as expected.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.