Skip to main content

Roadmap: Webhooks & OAuth

Two pieces of the API are designed but not built yet. This page exists so you can plan around them honestly, rather than discovering the gap partway through an integration.

Webhooks​

Not implemented. There's no way to register an endpoint, and nothing gets delivered — calling any webhook-related route today would fail.

When webhooks do ship, the shape is planned around booking and membership lifecycle events (a booking being created, confirmed, paid, cancelled or checked in; a membership being assigned, paid, or changing status) — but the exact event names and payloads are still a design, not a contract, so nothing here is final enough to build against yet.

If your integration needs to know when something happens today, the only option is polling — list bookings or memberships on a schedule and diff against what you saw last time.

OAuth​

Also not implemented. There's no way for a third-party app to request access on a host's behalf across several spaces — today, every integration works with a single API key, minted by hand for one space at a time.

Scopes that exist but don't do anything yet​

Three scopes show up when creating a key, but grant nothing to call today:

  • booking_types:write
  • content:read
  • webhooks:manage

If you see one of these in the scopes table, it's here for the same reason — designed, not shipped. Building against them now will only get you insufficient_scope even after granting them.

What's real right now​

Everything else in this section — public reads, guest booking, API keys, and the full bookings, booking-types, members and memberships surfaces — is live. See Resources for the complete list.