Developer API

Build directly on CueGuest with a secure API key.

Use the public v1 API to list properties and create guest guide links from your own systems.

Start with ZapierView API reference
CueGuest Developer API
GET/v1/properties

List properties

POST/v1/guest-links

Generate a guest link

POST/integrations/api-key

Create API key

Generate an API key

Create one active integration key from the CueGuest Integrations page. The full key is only shown once.

Connect Zapier

Paste your key into Zapier, choose a property, then generate a guide link from your trigger.

Rotate safely

Rotate or revoke a key at any time. Existing integrations stop using old keys immediately.

Zapier

Automate guide links from bookings, forms, or spreadsheets.

The Zapier path is best when your booking data already lands in another tool. CueGuest receives the guest and stay details, then returns a shareable guide link.

1

Create an API key

Open Integrations in CueGuest and generate a key.

2

Connect CueGuest in Zapier

Paste the key when Zapier asks you to authenticate.

3

Choose Generate Guest Guide Link

Map property, guest name, dates, email, and phone from your trigger.

4

Send the link

Use Gmail, WhatsApp, Slack, or your CRM to deliver the generated link.

Google Sheets

New row creates a guest guide link for a reservation.

Forms

New enquiry or check-in form response becomes a guide link.

CRM stages

Generate the link when a guest moves into a booked stage.

Email handoff

Pass the link to Gmail, Outlook, or a messaging step.

Developer API

Use a bearer token to create guest links from your own systems.

The v1 API is intentionally small: list your properties, then create guest guide links with real booking details.

Base URL

https://cueguest-api.jarred-smith-074.workers.dev

Authentication

Send your integration key in the Authorization header on every request.

Authorization: Bearer cg_live_...
GET/v1/properties

List active properties on your account.

POST/v1/guest-links

Generate a time-limited guest guide link.

curl -X POST https://cueguest-api.jarred-smith-074.workers.dev/v1/guest-links \
  -H "Authorization: Bearer cg_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "propertySlug": "sea-view-apartment",
    "expiresInDays": 14,
    "reservationLabel": "Smith - Apr 2026",
    "checkinDate": "2026-04-10",
    "checkoutDate": "2026-04-14",
    "guestEmail": "guest@example.com"
  }'
{
  "id": "token_id",
  "guestLink": "https://cueguest.com/g/sea-view-apartment/AbCd3FgH1jKl",
  "token": "AbCd3FgH1jKl",
  "propertyId": "prop_abc123",
  "propertySlug": "sea-view-apartment",
  "reservationLabel": "Smith - Apr 2026",
  "checkinDate": "2026-04-10",
  "checkoutDate": "2026-04-14",
  "guestEmail": "guest@example.com",
  "expiresAt": "2026-04-24T00:00:00.000Z",
  "status": "active",
  "createdAt": "2026-04-10T08:00:00.000Z"
}

Troubleshooting

Common integration checks

If a workflow fails, start with authentication, property matching, and date fields.

Confirm the key starts with cg_live_ and is sent as a bearer token.
Use either propertyId or propertySlug, not a property display name.
Keep expiresInDays between 1 and 90.
Rotate the key if it may have been copied into the wrong tool.

Webhooks are next

Today, use Zapier triggers or polling. Native webhooks for guest guide events are planned for a future release.

Need a hand with your first workflow?

Send us the tool you use for bookings and we will help you map the first automation cleanly.

Contact supportOpen Integrations