Skip to content
Sections

Guides

Guest communications

Deliver inbound messages and outbound delivery receipts.

Configure access

Configure the communication provider in the venue’s Guests communication settings. The provider ID and issued webhook secret identify the inbound channel. This protocol is for a configured messaging connector, not general guest-record access.

Cabinet route: /venues/:venueId/guests → Settings → Providers. Required permission: guests.providers.manage. Keep the selected provider active and copy its issued webhook secret once.

First successful workflow

Follow these steps in order. Open each method for its exact body, required headers and response schema.

  1. For inbound messages, send provider event/message identities, source contact, body and occurrence time.
  2. For outbound delivery events, send the referenced provider message identity and delivery state.
  3. Sign timestamp + "." + JSON.stringify(parsed DTO) with UTF-8 secret and base64url output. Read whether the event was newly applied or replayed.

State, retries and recovery

Provider event/message identities control deduplication. Repeating a signature alone is not a universal replay failure for this profile. Delivery updates preserve previous attempts; unknown referenced messages require reconciliation.

Hallify uses essential cookies and optional analytics.

Essential cookies keep sign-in, locale, and theme preferences working. Analytics is off until you choose to allow it.