Documentation Vacation rentals and PMS Zeevou

Rentals integration

Zeevou

Zeevou integration overview
  • CategoryRentals
  • AuthOAuth

Overview

Zeevou is a short-term-rental PMS. The property catalog surface holds no credential of its own: it reads through the connected Zeevou messaging channel's token, which is the one place that mints, refreshes and re-mints for the organisation. Each catalog row is one unit type, not one building, so the AI can distinguish between the flats inside a property.

What MessageMind can do with it

  • Import your Zeevou unit types as rows in the AI's property catalog, keyed on the unit type id, so the AI can distinguish between flats inside the same building rather than treating a property as one bookable thing.
  • Receive Zeevou callback webhooks for booking (insert, update, remove), guest (update) and property (insert, update, remove) events against a per-tenant /zeevou/:zeevouId path, with the fine-grained /:type/:event variant handled too.
  • Poll reservations as a safety net on a cursor-based walk, since Zeevou's booking projection carries no event type or organisation and a callback alone cannot be trusted as the source of truth.
  • Check availability for a stay, and look up reservations and booking requests from the AI's rental tools.
  • Treat a booking request as a stay in its own right, keyed separately from a booking so the two are never confused in the ledger.
  • Retry failed Zeevou callbacks on demand through a dedicated endpoint when a delivery was dropped on the MessageMind side.
  • Patch the stored host email list for an account when a Zeevou host identity changes without the full OAuth app being rotated.
  • Trigger a one-off property sync from the integration card (POST /zeevou/sync-properties) without waiting for the daily tick.

Requirements

  • A Zeevou account with API access.
  • A connected Zeevou messaging channel on the same MessageMind account (it owns the OAuth credential and token).
  • Only one property-management system may be connected per MessageMind account. Disconnect another PMS before connecting Zeevou; reconnecting the already connected PMS is supported.

How to connect

  1. First connect the Zeevou messaging channel on the channels page using your Zeevou Client ID and Client Secret.
  2. In MessageMind, open Integrations and select Zeevou. Save (no credential is pasted here).
  3. MessageMind re-validates the channel's token against Zeevou and reads your organisation identity. A rejected token asks you to reconnect the channel.
  4. On success, only identity and provenance (channel link, organisation id, organisation name) are stored on the integration. The secrets stay on the channel document.

Authentication and permissions

Mechanism
OAuth2 via the connected Zeevou channel; the catalog integration itself holds no credential.
Credentials
The Zeevou channel document owns the Client ID, Client Secret, and the access and refresh tokens. The catalog integration stores only the channel link and organisation identity.

Available data and actions

Reads

  • Your Zeevou properties, unit types and units, read inline so the whole account comes back in a handful of requests.
  • Reservations and booking requests, with a cursor-based change walk every poll tick and a two-hour overlap on updated_at to tolerate Zeevou's projection latency.
  • Reviews, with a multi-day overlap because Booking.com reviews ingested through Zeevou can land days after they were written.
  • The organisation identity returned by the OAuth handshake, used to prove the credential and to tag which Zeevou account the connection belongs to.
  • Signed Zeevou callbacks for booking insert, update and remove, guest update and property insert, update and remove.

Writes

  • Replies sent through the connected Zeevou messaging channel to supported guest threads. Property catalog and reservation tools do not create or modify bookings or properties.

AI agent use cases

  • Answer guest questions about a specific flat (unit type) rather than only the whole building.
  • Confirm a reservation's dates after the fact, or acknowledge a booking request before it becomes a confirmed booking.
  • Trigger follow-ups on OTA reviews that Zeevou imported from Booking.com and the other channels.
  • Hold the AI's rental tools (availability, reservation lookup, booking-request lookup) against a single short-stay PMS without a channel-manager layer in between.

Configuration

  • The booking webhook has never been observed carrying type, event or organisation, so a callback that does not name a booking only wakes the owner's poll.
  • Change walks list by updated_at with a two-hour overlap and remember recent (id, updated_at) pairs across passes.
  • Zeevou latency is the real hazard rather than throttling; some endpoints have measured up to 15 seconds.

Example workflows

Connect

  1. You connect the Zeevou messaging channel with your Client ID and Client Secret.
  2. You open the Zeevou integration and save.
  3. MessageMind validates the channel's token, reads the organisation identity and stores channel link and organisation identity.

Limitations

  • Without a connected Zeevou channel there is nothing to authenticate the catalog with; the integration refuses to connect.
  • Zeevou does not publish a bookings-list projection with an event type, so a callback is a signal rather than a source of truth; the ledger depends on the poll.
  • Zeevou latency can be high. A background read waits briefly for Zeevou's slow connects and retries a limited number of times.
  • The property catalog does not create or modify bookings, guests or properties. The connected Zeevou messaging channel can send replies in supported guest threads.

Troubleshooting

Connect fails asking you to connect the Zeevou channel first.

The catalog has no credential of its own. Connect the Zeevou channel on the channels page, then come back to Integrations and save Zeevou.

Connect says Zeevou rejected the channel's credentials.

Reconnect Zeevou on the channels page with a fresh Client ID and Client Secret, then save the integration again.

A newly added property is not yet visible to the AI.

A property callback runs the catalog pass; without it, the daily tick picks the change up on the next run. The roster also refreshes on a short cache.

Disconnect and reconnect

  • Open Integrations and Zeevou in the dashboard and choose Disconnect. Only the integration's provenance row is removed; the Zeevou channel keeps its credentials and keeps running.
  • To reconnect, make sure the Zeevou channel is still connected and save the integration again.