Connected ecosystem

Integrations & API.
Onzane does not work in isolation.

Connect payments, access control and number plate recognition with Onzane. Integrate your organisation’s software through Business API too.

Explore integrations View Business API

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.

  1. 01

    External system

    The software, process or device that needs to exchange information or perform an action.

  2. 02

    Integration layer

    APIs, credentials, rules and adapters control how the connection works.

  3. 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.

Available integrations

Specialist technology.
Connected to your community.

Payments, access and vehicles share the context of Onzane. Explore what each integration provides and how it fits into day-to-day management.

01

Payments

Connect payment collection with the resident experience.

Explore payments in Onzane

Stripe

Payments from the app

Onzane integrates Stripe to process resident payments within the platform’s payment collection workflows.

02

Access control

Apply community permissions to doors and shared facilities.

Explore access control

Shelly

Relays, sensors and connected spaces

Operate doors and mechanisms with compatible relays and receive sensor readings or states linked to community facilities.

Recommended hardware

Nuki

Smart locks

Integrate compatible Nuki locks with Onzane permissions to manage access from the community platform.

IOPark

Access to shared spaces

Integrate compatible IOPark systems with Onzane to manage access from the community platform.

Watchman Door

Connected locks

Integrate compatible Watchman Door locks with Onzane permissions to manage access to shared spaces.

03

Number plate recognition

Identify vehicles at community garage and car park entrances.

Explore garage access

Hikvision

Vehicle identification by number plate

Connect compatible Hikvision cameras for number plate recognition within Onzane’s garage access control workflows.

Dahua

Number plate recognition in garages

Integrate compatible Dahua cameras to identify vehicles by their number plates and connect those readings with Onzane access control.

Compatibility is assessed for each installation.

For hardware, we review the model, firmware and connectivity to confirm which functions your community can use.

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.

01

Management software

Reduce duplicate data entry and keep selected processes coordinated.

02

Financial processes

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

03

Access control

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

04

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.

  1. 01Analyse

    Define the objective, systems involved and current workflow.

  2. 02Set boundaries

    Specify data, operations, permissions, frequency and responsibilities.

  3. 03Integrate

    Configure credentials or devices and develop an adapter where required.

  4. 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 integrates compatible Shelly, Nuki, Watchman Door and IOPark access equipment, plus Hikvision and Dahua cameras for number plate recognition. Shelly is the recommended option for compatible new installations.

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