Docs/Knowledge Base/PMS Guides

Zeevou API

Zeevou exposes an OAuth 2.0 REST API (API Platform, JSON) covering organisations, properties, unit types, units, rate plans, nightly rates, availability and bookings; a unit type holds one or more units and a booking is allocated to one of them.

Written from running this integration in production. Last checked against the Zeevou API on 12 October 2026.

What the Zeevou API is

Zeevou is a property management system, channel manager and direct-booking website for serviced apartments, aparthotels and vacation rentals. Its model runs top-down: an organisation has properties, each property has unit types, and each unit type holds one or more units.

A booking belongs to a unit type and is auto-allocated to a unit, which the host can change. Prices live on rate plans, night by night.

Through Repull: each unit type is a listing with kind: "room_type", its units are listed under it, and its property is the hotel (GET /v1/hotels). Bookings carry the allocated unit, and availableUnits on the calendar is the number of units left that night.

How to get Zeevou API access

  1. 1.Pick Zeevou in Repull Connect (or create a session with allowedProviders: ["zeevou"]).
  2. 2.Sign in to Zeevou and allow access. Repull holds the partner app; you never handle client ids or secrets.
  3. 3.Repull names the connection after your Zeevou organisation and starts the first import.

Access tokens are renewed automatically. Disconnecting in Repull, or revoking the app in Zeevou, stops the sync.

What will bite you

From running this integration in production and reading the vendor's documentation line by line.

Units must be active to sell

A unit type only has availability when its units are active in Zeevou. Draft units come through as inactive, and their unit type reads as fully booked until they are activated.

One rate plan is written

Price, minimum/maximum stay, closed to arrival/departure and stop-sell are read from and written to the unit type’s default rate plan. Derived or channel-specific rate plans are left alone.

No webhooks

Zeevou callbacks carry no signature Repull can check, so Repull polls bookings by their last update time, about every minute.

Messages are read only

Guest messages are read from Zeevou’s inbox per booking. Zeevou’s API has no endpoint to send one, so replies go from Zeevou or the booking channel.

What it costs to keep working

The API is broad and consistent, but the hotel model and token handling are yours to get right.

  • •OAuth with refresh tokens that rotate: every refresh revokes the previous token, so a second process refreshing at the same time logs you out.
  • •Mapping unit types, units and their availability onto your own model.
  • •A polling loop for booking changes.

The same job, both ways

Zeevou directly

curl -s 'https://{zeevou-host}/apis/bookings?updated_at%5Bafter%5D=2026-10-01T00:00:00Z&page=1&limit=100' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

# Refresh the token before it expires (and save the new refresh token), then poll again.

Through Repull

curl -s 'https://api.repull.dev/v1/reservations?limit=100' \
  -H 'Authorization: Bearer sk_live_YOUR_KEY'

# Zeevou bookings, with the allocated unit, in the same shape as every other PMS.

Why use Repull for Zeevou

Your next customer may not be on Zeevou

If you only ever need one Zeevou organisation, use its API directly — you would be adding a layer you do not need. The cost arrives with the second system.

Hotel model included

Unit types, units and units left per night come through the same kind, hotel, unitCount and availableUnits fields as Cloudbeds and Mews.

Tokens handled

Repull renews and stores Zeevou’s rotating tokens for every connected organisation.

Polling handled

Booking changes reach your webhooks without a loop of your own.

Connect Zeevou through Repull

Create a key, connect a Zeevou account with the credentials Zeevou issues, and read reservations in the same shape as every other system you support.

Frequently asked questions

Does Repull support Zeevou multi-unit properties?

Yes. Each unit type is a listing with its units under it, the property is the hotel, and the calendar gives the units left per night.

Can I send guest messages to Zeevou bookings?

Not yet: Zeevou’s API has no endpoint to send a message. Repull reads the messages; replies go from Zeevou or the channel.

Does Repull receive Zeevou webhooks?

No. Repull polls Zeevou about every minute and sends you its own webhooks for the changes.

Which prices does Repull write?

Nightly price, minimum and maximum stay, closed to arrival/departure and open/closed nights, on the unit type’s default rate plan.

The other systems Repull connects

Reference

Auth Type

OAuth 2.0 (authorization code)

Required Fields

Supported Operations

✓ listings
✓ reservations
✓ calendar
✓ messages
— webhooks
✓ guests

Connection Guide

Pick Zeevou in Repull Connect, sign in to Zeevou and allow access. Repull starts importing your properties, unit types, units and bookings straight away.

Notes

  • • Each Zeevou unit type is a listing; its units are the rooms, and its property is the hotel
  • • No webhooks: Repull polls Zeevou about every minute
  • • Guest messages are read only: Zeevou’s API cannot send them
  • • Calendar writes go to the unit type’s default rate plan; unit counts are Zeevou’s units and are never written
  • • In beta while Zeevou certifies the integration
AI