Sandbox & Testing

Every workspace gets sandbox mode with pre-seeded test data. Use sk_test_ prefixed keys to access it. No PMS connection needed.

Picking a key

Newly issued keys carry the environment in their prefix: sk_test_ routes to the sandbox, sk_live_ routes to your real PMS data. Legacy bare-hex keys still work — they default to live and stay valid until you revoke them. See Authentication → Legacy keys for details.

What's in the sandbox

5 Properties

Malibu, Aspen, Austin, Tahoe, San Diego

8 Reservations

Multi-platform: Airbnb, Booking, VRBO, direct

16 Guests

With contacts and language preferences

4 Reviews

With ratings and public review text

450 Calendar Days

90 days per property with pricing

4 Conversations

With guest/host message threads

Failure Scenarios

Special IDs trigger specific errors — like Stripe's test card numbers:

GET /v1/reservations/900001409 Overbooking conflict

GET /v1/reservations/900002504 PMS timeout

GET /v1/reservations/900003429 Rate limited

GET /v1/reservations/900004401 Auth expired

GET /v1/properties/900001404 Deleted property

Seed sandbox data

curl -X POST https://api.repull.dev/v1/sandbox/seed

Idempotent — safe to call multiple times. Only affects your sandbox customer.

Previous← OAuth Connect NextSchema Adapters →