API for management systems
Your PMS. One connection to smart homes.
octopancy is the smart-home channel manager for your PMS or management system. One shared API connects your booking and operational workflows with supported heating controls, door locks and key safes. Your system provides the plan; octopancy coordinates the corresponding controls.
One interface for different providers
Build a connection to octopancy instead of implementing a separate smart-home workflow for every provider in your PMS. octopancy handles technical mappings and commands for connected devices through their providers.
Homematic IP links heating with occupancy, Nuki adds digital door access and masunt supports physical key handover. Available functions depend on the customer’s devices, setup and authorised integrations.
Turn a booking into an on-site workflow
Send reservations with units, people and time windows. These provide the basis for time-limited control permissions and scheduled actions, such as setting a target temperature before arrival and reducing it after departure.
Cleaning, maintenance and independent access orders can also be organised through the shared interface. Decide which tasks your integration owns and which your customer manages directly in octopancy.
Your PMS remains responsible for its data
Booking management stays in your system. External identifiers link your properties, units and reservations to the corresponding records in octopancy. Existing spatial structures can be linked; with the appropriate permissions, your integration can also create and maintain locations, areas, rooms and units.
Authority is defined per record. A new connection does not automatically take control of existing data. This allows integration with businesses that have already configured their spaces and devices in octopancy.
One integration serving multiple customers
As a PMS provider, you use a shared integration contract. Each connected customer has their own workspace, device connections and permissions. Your integration can access only explicitly connected customers and authorised tasks.
Smart-home accounts connect to octopancy for each customer. Provider-specific technical differences stay behind the common interface rather than becoming separate booking workflows in your software.
A clear foundation for your development team
The integration uses a versioned REST API with a shared OpenAPI contract. It describes endpoints, data models, authentication and error responses.
We begin by agreeing on the data scope, authoritative systems and a concrete use case. Then we verify customer mappings, spatial structures and the complete workflow from reservation to device action together.
An everyday example
From a PMS booking to a prepared holiday apartment
An agency manages its holiday apartments in your PMS. For an arrival on Friday at 4 pm, it sends the property, guest and stay period to octopancy. A scheduled heating action sets the agreed target temperature before arrival. The guest uses the configured door control during their access window. After departure, the planned temperature setback runs and a linked cleaning assignment has its own time window. Booking management and smart-home controls work together.
Good to know
Your questions, answered.
Who is this API for?
Providers and development teams building property-management systems, booking platforms and other management software. Custom operational software can connect through the same interface.
Does octopancy replace our PMS or booking channel manager?
No. Your PMS retains its booking and management responsibilities. octopancy connects those workflows with smart-home controls and time-limited access. The smart-home channel manager does not distribute accommodation listings to booking portals.
Do we need to integrate every feature at once?
No. Scope depends on the tasks authorised for your integration. Start with a clearly defined workflow and connect spatial management, reservations or workforce planning as appropriate for your product.
Can customers keep their existing spaces and devices?
Yes. External identifiers can link existing records with your system. Linking does not replace device connections or automatically transfer data authority.
Is every manufacturer feature available through the API?
Available workflows depend on supported octopancy functions and the specific device integration. A common API does not mean every device has the same capabilities. We work with you to identify the right combination for your use case.
Explore what connects