Skip to main content

Endpoint

Updates an existing in-house guest’s details. Uses partial update semantics — only include the fields that changed. The guest is identified by pmsGuestId.

Headers

Request body

Only include pmsGuestId (required) and the fields that changed:

Field reference

Room changes are automatic. When you update roomNumber, RecepAI handles the room move internally — deactivating the old room assignment and creating a new one. You don’t need to check out and re-check-in the guest.

Responses

Success (200)

The response includes a changes object showing exactly what was modified:

No Changes (200)

If all submitted values are identical to the current values, the response returns 200 with status: "unchanged" and an empty changes object:
This is not an error — it simply means the data was already up to date. Your integration can treat "unchanged" the same as "updated" for success handling.

Guest Not Found (404)

Returned when no active guest with the given pmsGuestId exists:
This error means the guest was either never checked in via the PMS API, or has already been checked out. If you receive this unexpectedly, use GET /guests to see which guests are currently active.

Room Occupied (409)

If you try to move a guest to a room that’s already occupied:

Idempotency

This endpoint requires an Idempotency-Key header. Resending the same key within 24 hours replays the original response instead of repeating the operation, and a 4xx response does not consume the key. See Idempotency for the rules and the recommended key format.

Example