Connected ecosystem

Integrations & API.
Onzane does not work in isolation.

Connect the software your organisation already uses to Onzane through Business API and add third-party devices to extend the platform into physical spaces.

View the integration model View Business API

Existing software Internal processes Devices

API · IntegrationsBUS / v1

OOnzane core

Onzane appWeb panelsCommunity operations

An open platform where it adds value

Integrate data, processes
and physical spaces.

Every integration starts with a specific need. Onzane retains the community context while the external system or device provides a specialist capability.

01
External system
The software, process or device that needs to exchange information or perform an action.
02
Integration layer
APIs, credentials, rules and adapters control how the connection works.
03
Onzane
Information remains linked to communities, properties, residents, permissions and operations.

A useful integration prevents duplicate work without losing control over who can access each item of data or action.

Software integration

Business API to connect
your organisation’s operations.

Business API allows authorised applications to communicate with Onzane over HTTPS and JSON. Its current public contract includes financial operations for communities and properties, plus resident-status queries.

Currently documented scope

Community finances: Read and manage financial movements linked to a community.
Property finances: Operations on movements associated with a home, unit, garage or other property.
Resident status: Locate residents within the authorised scope and query their status and open incidents.

Controlled technical access

Bearer token: Each integration authenticates with a Business credential.
Defined scope: The token is tied to its user and Onzane administration.
Revocable credential: It can be replaced or revoked from the panel whenever needed.
Versioned contract: The technical reference is also published as OpenAPI 3.0.3.

Authenticated request

GET /bus/v1/communities/{reference}/finances

Authorization: Bearer ••••••••••••
Accept: application/json

// 200 OK · JSON · UTF-8

Conceptual example based on the public Business API reference.

Open technical documentation

Device integration

Third-party hardware.
The building connects too.

Onzane integrates with specialist manufacturers when a device provides a specific physical capability. Compatibility is validated by model, installation and use case.

01Watchman Door

Locks and access

Integration with compatible locks to apply Onzane permissions at selected access points.

02Shelly

Relays and actuation

Relays to operate compatible doors, circuits or mechanisms using platform rules and permissions.

03Shelly

Sensors and status

Compatible sensors to receive status or measurements and link them to community facilities.

Shelly is Onzane’s recommended hardware ecosystem for compatible new implementations.

Explore community home automation

Connect with a purpose

Integration starts with
the outcome you need.

Scope is defined by the data, processes and actions Onzane and the external system need to share.

Management software

Reduce duplicate data entry and keep selected processes coordinated.

Financial processes

Exchange community or property movements within the scope published by Business API.

Access control

Turn digital permissions into actions on compatible locks, relays and other equipment.

Facility monitoring

Collect sensor signals and retain them alongside the facility context.

Guided technical implementation

First define the exchange.
Then connect it.

A stable integration requires systems, owners, data, permissions and error behaviour to be identified before production.

01Analyse
Define the objective, systems involved and current workflow.
02Set boundaries
Specify data, operations, permissions, frequency and responsibilities.
03Integrate
Configure credentials or devices and develop an adapter where required.
04Validate
Test normal cases, errors, revocation and traceability before activation.

Not every connection is the same.

Some can use the current Business API contract or already compatible devices. Others require specific analysis and development.

Before connecting

Questions about integrations and API.

Actual scope depends on the external system, workflow, data boundary and physical installation.

01What is Onzane Business API?

It is the API for connecting third-party applications to Onzane over HTTPS with JSON responses. It uses Bearer tokens associated with a user and their administration.

02Which operations does it currently provide?

The current public reference covers financial operations for communities and properties and resident-status queries. The contract can evolve through versioning.

03Can we integrate our existing software?

Yes, when the required workflow is covered by the API or a specific integration can be developed. Data, permissions, volume and expected behaviour are reviewed first.

04How is API access controlled?

Each integration uses a Business token associated with a user and administration scope. The credential can be revoked when no longer needed or when it must be replaced.

05Which hardware does Onzane integrate with?

Onzane currently provides integrations for selected Watchman Door and Shelly devices. Shelly is Onzane’s recommended option for compatible new implementations.

06Is every device from those manufacturers compatible?

Not necessarily. Compatibility depends on model, firmware, connectivity, installation and use case. Onzane validates each project before implementation.

Connect without duplication

Tell us which system or device you need to integrate.

We will review the workflow, available scope and safest way to connect it to Onzane.

Assess my integration