Developers
Build with Zuesie without bypassing the guardrails.
Developer access is being opened in stages. The goal is a small stable API, signed webhooks and clear integration boundaries for automation platforms and AI tools.
API access
Zuesie’s API surface is being documented around stable property, reservation, pricing and integration workflows. Public credentials will be scoped per organisation rather than exposing internal Shannon services.
Webhooks
Third-party platforms such as Make can receive governed events from Zuesie. Webhook delivery should be signed, retryable and auditable before it is exposed to customers.
AI integrations
Zuesie is designed so AI tools can work from explicit, permissioned interfaces rather than scraping the PMS. Shannon AI remains the native automation layer; external AI integrations will use the same governed API model.
Security model
Organisation isolation, scoped credentials, audit trails and explicit permissions are requirements for any developer integration. Internal Shannon endpoints are not part of the public API contract.
Launch integrations
PriceLabs and channel distribution are the first commercial integration priorities. Generic API keys, Make-style webhooks and broader AI integrations will follow once the contracts are stable enough that customers are not rebuilding automations every week.