Guest portal

Until now the link of each booking did one thing: let the guest register and sign. With the portal on, that same link is also the guide to the stay, with your branding and in the guest’s language. There is no second link and no app: whatever your PMS already hands out, or whatever our emails send, leads to the portal.

What the guest sees

The portal is split into four sections, with an icon bar at the bottom on mobile and a side menu on desktop. Only the sections with content show up, and the section travels in the link (#casa), so a message can point straight at one of them.

Every text goes per language: the guest reads theirs, failing that Spanish, failing that whatever exists. Categories, manual topics and phone types are translated on their own; proper names (a restaurant, a taxi company) are not.

When the codes open

The access instructions, the codes and the wifi sit behind a lock that opens when two conditions hold at once:

The codes do not travel with the page: the guest taps “Show the codes” and they are fetched at that moment. Each time is logged — when, from which network (truncated: last octet removed) and why it was allowed — for 90 days, and you can read it over the API. What that log never stores is the codes themselves.

Unlock now. The guest is at the door and has not signed: a button on the booking page — and an API call — opens the access without waiting for the registration or the window. Who opened it and when is recorded, it still closes at the end of the check-out day, and it can be undone.

Switching it on and tuning it

In the panel, Guest portal → Settings. Over the API, the guestPortal object of /settings. Like every other setting, only what you send changes.

curl -X PATCH https://api.kinapi.es/api/v1/settings \
  -H "ocp-apim-subscription-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{"guestPortal":{"enabled":true,"hoursBefore":24,"phone":"+34600000000"}}'

Common content, blocks and own content

Fifty properties are not filled in one by one. Seven sections of the portal can be shared — arrival, parking, the house manual, the house rules, the area, departure and the useful numbers — and they are written in three places:

For each section of each property you decide where it comes from, and the rule is always the same:

In the panel, the Guest portal entry of the menu has three tabs: Properties (a table with the state of every section on every property — ✓ own, ≡ common, ⧉ block — and bulk assignment of a variant to several properties), Common and Settings. On each property, every shared section has its selector — common, a variant, own or hidden —, and the page has “Copy from another property” (everything but codes and wifi) and “Previous / Next” to walk the portfolio without going back to the list.

The common content of the account

The PUT replaces the whole common content: a section you leave out is removed. Read, change, write. The read returns only the sections with content.

curl -X PUT https://api.kinapi.es/api/v1/portal/common \
  -H "ocp-apim-subscription-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "departure": { "es": "Deja las llaves en la caja y cierra la puerta al salir.", "en": "Leave the keys in the box and shut the door behind you." },
    "showHouseRules": true,
    "usefulNumbers": [
      { "type": "taxi", "name": "Radio Taxi", "number": "+34 956 000 000" },
      { "type": "centroSalud", "number": "+34 956 111 111" }
    ]
  }'

Blocks

curl -X POST https://api.kinapi.es/api/v1/portal/blocks \
  -H "ocp-apim-subscription-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "section": "parking",
    "name": "Alameda car park",
    "content": {
      "parking": { "es": "Plaza 14 del parking de la Alameda, a 200 m. El mando abre la barrera.", "en": "Bay 14 at the Alameda car park, 200 m away. The remote opens the barrier." },
      "parkingMapUrl": "https://maps.app.goo.gl/…"
    },
    "propertyIds": ["b8f3a2c1-…", "5c7d9e01-…"]
  }'

{
  "id": "3f9c…",
  "section": "parking",
  "name": "Alameda car park",
  "content": { "parking": { "es": "…", "en": "…" }, "parkingMapUrl": "https://maps.app.goo.gl/…" },
  "propertyIds": ["b8f3a2c1-…", "5c7d9e01-…"],
  "updatedAt": "2026-10-23T10:00:00.000Z"
}

The id is what goes into a property’s origins as block:3f9c…. Deleting a block sends its properties back to their own or the common content; nothing of theirs is deleted.

The portal of a property

What belongs to each accommodation: the shared sections above, plus what can only be its own and where each section comes from. The PUT replaces the whole portal, codes and wifi included: what you leave out is removed.

curl -X PUT https://api.kinapi.es/api/v1/properties/b8f3a2c1-…/portal \
  -H "ocp-apim-subscription-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "houseMapUrl": "https://maps.app.goo.gl/…",
    "arrival": { "es": "Portal verde junto a la farmacia. 2.º izquierda.", "en": "Green street door next to the pharmacy. 2nd floor, left." },
    "access": { "en": "The key box is to the right of the street door; the door code opens the garage too." },
    "codes": [ { "type": "portal", "value": "4821" }, { "type": "cajaLlaves", "value": "0719" } ],
    "wifi": { "network": "Sol3B", "password": "tarifa-2026" },
    "manual": { "climatizacion": { "en": "The thermostat is in the hallway; 21 ºC is plenty." } },
    "origins": { "parking": "block:3f9c…", "area": "hidden" }
  }'

{
  "propertyId": "b8f3a2c1-…",
  "houseMapUrl": "https://maps.app.goo.gl/…",
  "arrival": { "es": "…", "en": "…" },
  "access": { "en": "…" },
  "codes": [ { "type": "portal", "value": "4821" }, { "type": "cajaLlaves", "value": "0719" } ],
  "wifi": { "network": "Sol3B", "password": "tarifa-2026" },
  "manual": { "climatizacion": { "en": "…" } },
  "origins": {
    "arrival": { "source": "own" },
    "parking": { "source": "block", "blockId": "3f9c…" },
    "manual": { "source": "own" },
    "houseRules": { "source": "common" },
    "area": { "source": "hidden" },
    "departure": { "source": "common" },
    "usefulNumbers": { "source": "common" }
  },
  "updatedAt": "2026-10-23T10:05:00.000Z"
}

The access of a booking

Whether the guest of a booking can already see the codes, since or until when, whether someone unlocked it by hand and when they looked. The POST is “Unlock now” — signed api: plus the label of your key — and the DELETE undoes it. All three return the same object; never the codes, which belong to the property.

{
  "enabled": true,
  "state": "open",
  "closesAt": "2026-08-18T21:59:59.999Z",
  "openedBy": "unlock",
  "unlocked": { "at": "2026-08-14T13:02:11.000Z", "by": "api:PMS" },
  "reveals": [
    { "at": "2026-08-14T15:40:02.000Z", "network": "83.45.12.0", "reason": "unlock" }
  ]
}

A cancelled booking cannot be unlocked: 409 cancelled. There are no new webhook events: checkin.completed is still the moment the access opens, if the booking is already inside the window.

Check-in and check-out times

The code window and what the guest reads under Stay depend on the check-in and check-out times of the booking, and those resolve in a cascade: the booking → the property → the account → 16:00 / 11:00. A booking that brings its time keeps it; one that does not inherits the property’s (checkInTime and checkOutTime on /properties), and if the property has none, the account’s (stay on /settings).

From an agent

The MCP server has one tool per operation above, to configure the portal by talking:

"Put in the common content that the keys go in the box, and show the house rules"
"Create a parking block called 'Alameda car park' with this text and assign it to the six flats on Alameda street"
"Has the guest of booking 4821 seen the codes yet?"
"The guest of 4821 is at the door and has not signed: open the access for them"