Skip to content
Unitify

Integrations for HOA, condo and building management software

A management company or a developer rarely runs one system. There is an accounting or ERP system, a bank, door and intercom hardware, meters, and the messengers residents already use. Connecting them is usually quicker than people expect.

This page lists the kinds of system Unitify connects to, which way data moves, and what works today versus what is set up for your project. We describe categories, not a wall of logos, because a connection depends on the interface of your system, not on its name.

Short answer

Unitify connects to six kinds of system: accounting and ERP, payments and bank statements, access control and intercoms, meters and sensors, messaging channels, and anything that speaks the open API. Files, the GraphQL API and webhooks work today. A link to a specific system or device is set up per project, and we confirm it on a test building before you commit.

Six categories of system you can connect

Each page says what the category is for, what data moves and in which direction, what works today, how the connection is made and what you provide.

  • Accounting and ERP

    Keep your books where they are. Buildings, owners and balances come in by file or API; payments, requests and readings go out as Excel exports.

    See this category
  • Payments and bank feeds

    Card payments through a payment provider, bank statements loaded by file. The right provider depends on the country.

    See this category
  • Access control and intercoms

    Door panels, intercoms, gates and controllers with an API or SIP interface, brought into the resident app per project.

    See this category
  • Meters and sensors

    Readings from residents, files and your metering system's API; smart meters and sensors with an interface per project.

    See this category
  • Messaging channels

    Email, SMS, push and Telegram today; Telegram channel posting and chatbots through the API per project.

    See this category
  • Open API and webhooks

    A GraphQL API, webhooks, mini-apps and external sign-in for any system that can call them. The route for vendors.

    See this category

How a connection is made

Four ways in, and each is marked with what exists today.

  • Works today

    A file

    Excel or CSV import and export in the admin panel. The fastest start, and it needs no access to your other system.

  • Works today

    The open API

    A GraphQL API over buildings, owners, requests, meter readings and more, for a system that can call it. API access is part of the Pro plan.

  • Works today

    Webhooks

    Unitify calls an address when a request, contact or invoice changes, so your system hears about it at once. We set the subscription up for you.

  • Set up per project

    A device interface

    SIP, ONVIF, an HTTP API, or a Modbus or M-Bus gateway on the hardware. We connect hardware that exposes one of these under your project.

What works today and what is per project

The line between the two is the same on every category page.

  • Works today

    Works today

    Import of buildings, apartments, owners and meters from a file. Export to Excel of payments, requests, contacts, properties and meter readings. The GraphQL API and webhooks. Notifications by email, SMS, push and Telegram.

  • Set up per project

    Set up per project

    A link to your specific accounting or ERP system. Door, intercom and gate hardware. Smart meters and sensors. An automatic bank feed. Posting announcements into a Telegram channel.

What we need from you

  • Access or an export

    Open your current system to us, or send an export: buildings, apartments, owners and balances.

  • The interface description

    The API documentation of your system or the file format of its export. For hardware, the exact model and its interface documentation.

  • A test building or device

    One building, or one device, to prove the connection on before the rest.

For vendors: how to integrate with Unitify

Vendors are welcome. The terms are the same for everyone: an interface we can test, then a project.

  • Hardware vendors

    If your device exposes an API, SIP, ONVIF or a Modbus or M-Bus gateway, send us its interface documentation and a test unit. We assess the exact model and connect it under a project. We do not promise a ready-made plug-in for a model before it is tested.

    Write to [email protected]
  • Software vendors

    The open API documentation is public: the domain model, authorization and examples including webhooks. Read it, then tell us what your system needs to read or write.

    Open the API documentation
  • Mini-app builders

    A web service can run inside the Unitify admin panel or the resident app as a mini-app, using the Bridge library to talk to the host application.

    Open the Bridge documentation
  • Sign-in from your own service

    A service with its own users can act as an OpenID Connect provider so its users sign in to the Unitify API without a second password.

    Read how external sign-in works
  • Link to the right page

    If your documentation mentions Unitify, link to the category page that matches your product. It says in plain words what works today and what is set up per project, so your customers do not have to guess.

The honest limits

  • No list of ready-made plug-ins. A connection is project work and we confirm it before you commit. Nothing on these pages claims a ready connection to a named accounting system, device or messenger.
  • No live two-way sync with an accounting system out of the box. Files and the open API move the data today. A scheduled or event-driven exchange with your system is built per project.
  • Hardware without an interface cannot be connected. If a door panel, controller, meter or camera has no API, SIP, ONVIF or gateway, there is nothing to connect to. We check the exact model first.

Integrations: questions

Which systems can Unitify connect to?

Six kinds: accounting and ERP systems, payment providers and bank statements, access control and intercoms, meters and sensors, messaging channels, and any software that uses the open API. The category pages say what works today and what is set up per project.

Do you publish a list of the systems you already work with?

No, and on purpose. A connection depends on the interface of your system, not on its name, so we describe categories. The one exception is payments: the providers that have an adapter in the product each have their own page.

Is there a live two-way sync with my accounting system?

Not out of the box. Data moves by file and over the open API today. A scheduled or event-driven exchange with a specific system is built per project and assessed system by system.

How long does a connection take?

It starts with a test building, and the time depends on the interface of the system or device. We do not quote a fixed number of days before we have seen the interface.

Can a hardware or software vendor integrate with Unitify?

Yes. Hardware that exposes an API, SIP, ONVIF or a gateway is connected under a project. Software can use the public API documentation, webhooks and mini-apps. Write to us with the interface documentation.

Is API access included in every plan?

API access is part of the Pro plan. The live pricing page has the current plan details.

Related

Tell us which system you run

Start free with one building, no card and no call. Or book a walkthrough and name the systems and devices you want connected; we confirm each one before you commit.