NewReynt AI: a link becomes a finished listing
Calendar sync

A free night is free everywhere.

Reynt reads your portals’ calendars every hour and publishes a feed of its own back to them. Book somewhere else and those dates show as taken here too — without you re-entering anything.

No credit card required — after 14 days the trial ends by itself.

  • iCal both ways
  • Hourly sync
  • Token-protected feed
Calendar sync in the Reynt back office

Hourly

every connected calendar is fetched and reconciled

365 days

is how far ahead the feed Reynt publishes reaches

1 click

resets a broken feed and syncs it straight away

Availability that stays in step

iCal in and out — including everything that matters when an address stops answering.

Read in other calendars

Add as many iCal addresses per property as you need — booking portals, channel managers, or anything else that speaks iCal. Reynt fetches them every hour and blocks the dates they report, so a booking made elsewhere closes the night here as well.

  • Several feeds per property
  • Hourly sync in the background
  • Blocked periods keep the reason from the feed

Publish a feed of your own

Every property gets its own .ics address carrying confirmed bookings and the periods you blocked yourself, for the next 365 days. Put it into the portals and your Reynt bookings close those nights over there.

Token-protected and revocable

The feed address carries a token. Regenerate it whenever you like — which retires the old address — or revoke it entirely. Your calendar is shareable without being public.

Failures surface before they hurt

Every feed tracks its consecutive failures and the last error message. Reynt retries with a growing gap — from a quarter of an hour up to a day — parks an address that keeps failing, and reports it on the dashboard alerts card.

  • Failure count and message per feed
  • Retries with a growing gap
  • Alert on the dashboard

Pause and resume

Individual feeds can be paused without deleting them — handy when a portal is dormant for a season. A manual sync resets the failure count and the pause, and syncs immediately.

Only writes what actually changed

Reynt compares every fetched calendar against the previous state and writes only when the blocked dates genuinely differ. That keeps the history clean and the calendar quiet.

Synced automatically or entered by hand?

The same portals, the same bookings — without the fear of the double-booked night.

A booking on a portal

With calendar sync

Blocks those dates here automatically

Calendars kept by hand

Re-entered everywhere by hand

Reconciliation

With calendar sync

Hourly, without you doing anything

Calendars kept by hand

Whenever you remember

Double bookings

With calendar sync

Blocked periods come straight from the feed

Calendars kept by hand

Two portals, one free night, one problem

Failures

With calendar sync

Failure count, message, and a dashboard alert

Calendars kept by hand

You notice once it’s too late

Recovery

With calendar sync

Automatic retries, or immediate on request

Calendars kept by hand

Reconnect it by hand

Sharing your calendar

With calendar sync

One token-protected feed per property

Calendars kept by hand

Screenshots and phone calls

Four steps to a calendar that agrees

Connect it once — after that it runs in the background.

  1. 1

    Grab the address

    Copy the iCal address from the portal — or wherever else you list.

  2. 2

    Connect the calendar

    Store the address on the property — several feeds per property are fine.

  3. 3

    Share your own feed

    Reynt generates a token-protected .ics address that you paste into the portals.

  4. 4

    Let it run

    Hourly sync, automatic retries, and an alert when something stops answering.

What this means for you

No double booking because one portal didn’t know

Availability stays right without re-entering it

A broken feed is visible immediately

Share your calendar without making it public