Docs/Knowledge Base

Sandbox Test Scenarios

The sandbox environment provides pre-seeded data and magic IDs that trigger specific behaviors — like Stripe's test card numbers.

Pre-seeded Properties

Every sandbox workspace includes 3 properties out of the box:

  • Property 1 — Single-unit vacation rental (1 bedroom, 1 bathroom). Has active reservations.
  • Property 2 — Multi-unit apart-hotel (5 room types, 12 units). Mixed availability.
  • Property 3 — Boutique hotel (3 room types, 8 rooms). Includes reviews and guest conversations.

Test Reservations

Pre-seeded reservations cover all common states:

  • Confirmed — Upcoming bookings with full guest and payment details.
  • Pending — Awaiting host confirmation (inquiry flow).
  • Cancelled — Cancelled bookings with cancellation reason and refund data.
  • Checked-in / Checked-out — Past and in-progress stays.

Simulated Failures

Use these magic IDs to trigger specific error codes:

reservation:900001409 — Overbooking conflict
reservation:900002504 — PMS timeout (simulated slow response)
reservation:900003429 — Rate limited
reservation:900004401 — Auth expired (simulated token revocation)
property:900001404 — Deleted property
property:900002504 — PMS timeout

Seeding Fresh Data

Reset your sandbox to the default state at any time:

POST /v1/sandbox/seed
Authorization: Bearer sk_test_YOUR_KEY
X-Workspace-Id: YOUR_WS_ID

This clears all existing sandbox data and re-creates the default properties, reservations, guests, and conversations. Sandbox data is isolated per workspace.

AI