Skip to main content
legacy-v1 is temporary. It will be removed when KYC API v1 is retired, expected in 2027, and KYC will give you notice first.
If your system already reads guest messages from KYC API v1, KYC can set up your endpoint on the legacy-v1 payload version. You then receive each message in the same shape API v1 returns it, so you can switch from polling to webhooks without changing how you parse messages.

What stays the same

Everything except the resource works exactly as described in the rest of the Webhooks guide: Only guestcomm.message.created is available on legacy-v1.

Example

Resource fields

data.resource is the message exactly as KYC API v1 returns it, plus object and guestId.
There are two property IDs. data.propertyId is the property’s UUID, the same in every payload version. data.resource.propertyId is its API v1 ID, which is what your existing integration uses.

Handling the message text

Unlike the current version, a legacy-v1 payload contains the guest’s message text, and may contain links to images and attachments. Treat every payload as guest personal data: follow the PII guidance, store it only as long as you need it, and never log it.

Moving to the current version

Before legacy-v1 is removed, ask KYC to set up a second endpoint on 2026-11-01, with its own URL. Run both while you switch over. Both endpoints receive the same event with the same webhook-id, so deduplicate per endpoint, not across them. When you’re ready, KYC removes the legacy-v1 endpoint.