Log+Key

Open & connectable

Connect Log+Key to your systems

Log+Key is built API-first from the ground up — even our own web and app interface talks exclusively to that API. Whatever we use internally is open to your systems too. For common industry software we deliver ready-made connections, and we develop custom integrations together with you.

What we already connect

Integrations at a glance

  • UMO (Enovation)

    Key status flows automatically into scheduling. Official partnership with Enovation.

  • NEXUS Heim

    Users are automatically created, updated and removed in Log+Key from the master data in NEXUS.

  • Connext Vivendi

    In development — a two-way connection for key and resident data.

  • Custom integration

    Run your own software? We build the integration together with you. Get in touch.

Live in use

UMO — key status for scheduling

With our UMO integration, schedulers see in real time which keys are in circulation and which are ready to hand out. Status changes from Log+Key land automatically in the UMO system — no double entry, no parallel lists.

In development: the other direction. UMO tells Log+Key about upcoming jobs, so staff know which keys to take with them — and are warned if they accidentally pack the wrong one.

Log+Key is an official partner of Enovation, the company behind UMO.

UMO

Live in use

NEXUS Heim — users synced automatically

Anyone created, changed or deactivated as a staff member in NEXUS Heim is automatically the same in Log+Key. Master data stays where it is maintained — you don't maintain it twice, and nobody accidentally keeps access they should no longer have.

Typical use cases: residential and outpatient care, home emergency call services, and facilities running shifts.

NEXUS

Currently in development

Connext Vivendi — a two-way connection

We are currently building a two-way integration with Connext Vivendi. The goal: keep key responsibilities and relevant master data automatically consistent between both systems, so you neither enter data twice nor reconcile it by hand.

Do you use Vivendi and would like to take part in the pilot? Get in touch — we'd be glad to test it together.

VIVENDI

Built API-first

Everything Log+Key can do is available through the API

Log+Key was developed as an API-first application from the very start. Our own web and mobile interface communicates with the backend exclusively through this API — so it is not a bolt-on afterthought, but the product's central interface.

What that means for you: if you want to embed Log+Key into your own tools, dashboards or workflows, we're not talking about a "maybe" but about the "how". Custom apps, automated reports, a connection to a DMS or ERP — technically, it's possible.

We develop custom integrations on request. Talk to us about your specific requirement.

API

Coming soon

A public API for external developers — in preparation

We are currently preparing a public API that external developers can use to build their own integrations, extensions and tools around Log+Key. Documentation, authentication and a sandbox will follow.

Would you like to be among the first to get access? Let us know about your use case — we invite early-access registrants directly as soon as it's ready.

# Example request — create a key movement
curl -X POST https://api.log-key.de/v1/keys/move \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "keyId": "k_482",
    "fromUser": "u_22",
    "toUser":   "u_47",
    "note":     "Shift handover",
    "signed":   true
  }'

# 201 Created
{ "id": "mv_9a3f", "createdAt": "2026-05-18T07:14:33Z" }

Your system not on the list?

Ask us about your integration

We're in constant contact with more providers and also build custom integrations — from simple data imports to full two-way sync solutions. Describe your use case to us and we'll assess feasibility and effort.

Get in touch

Frequently asked questions

Integrations & API

  • Which integrations exist today, and which are in development?

    Live today: UMO (sending), NEXUS Heim (user sync). In development: UMO return channel, Connext Vivendi (bidirectional), Public API. On request: custom integrations into almost any system that has its own API or a documented interface.

  • Are you an official partner of Enovation / UMO?

    Yes. Log+Key is an official partner of Enovation, the maker of UMO. We are in regular contact on integration topics.

  • What does a custom integration cost?

    It depends on the target system and the scope — anything from a simple CSV import to a deep two-way integration is possible. In an initial call we clarify what you need and then give you a concrete quote. Request a consultation.

  • How does the data transfer work — does data flow to the EU or to the US?

    All Log+Key integrations run over our EU-hosted infrastructure. No data is transferred to US processors. Details on our security page.

  • Can you also read from our system, or only receive data?

    Both are possible, depending on the integration. With UMO we currently send status data and are implementing the return channel. With NEXUS we read user data. For custom integrations we clarify the data direction with your IT team.

  • We don't have an open API — is anything still possible?

    Often, yes. CSV/Excel exports, documented database views, SFTP drops or webhooks can frequently be connected. We assess the options in the initial call.

  • When will the Public API be available?

    We are deliberately not naming a date yet, so we are not boxed in and can deliver quality. If you would like early access: let us know and we will get in touch as soon as the early-access programme starts.