Integrations

Under Settings > Integrations, you manage connections to external systems and services—for example electronic door systems, timetable software, or accounting systems. ↗ Open in Locaboo

The sections below on help.locaboo.com walk you through each integration step by step.

Integration guides overview

The table maps each topic to a section on this page (anchor link).

Topic	What the guide covers	Guide on this page
SSO (SAML2/Shibboleth)	IdP, locaboo_roles, metadata, SAML login	↓ SSO
SSO (Microsoft Azure)	Azure AD with Locaboo	↓ Azure
API	REST API, reference, secret key	↓ API
WebUntis	Tenant ID, room mapping, timetable import	↓ WebUntis
Tapkey	Lock, account, Connect, resource assignment	↓ Tapkey
Comydo	Device ID, resources, “Digital locks” column	↓ Comydo
Salto KS	Cloud connection, resource mapping, lead/wrap-up	↓ Salto KS
Evva Airkey	API key, mapping, lead/wrap-up	↓ Evva Airkey
Primion	Enablement, customer Primion ID, SFTP export	↓ Primion
Outlook	Calendar sync Locaboo → Outlook (beta)	↓ Outlook
Spielplus (DFBnet)	Match import, venue numbers, CSV	↓ Spielplus
SPF	DNS/SPF for mail from your domain	↓ SPF
2D maps	Building/site plans on the platform	↓ 2D maps

Also related: overview of electronic locking systems: Electronic door lock systems.

---

Electronic door access

Locaboo can be connected to various electronic locking systems. Customers and staff can then open doors directly from the booking platform—access rights are tied automatically to booking times.

Benefits of electronic door locks:

• No key management – No handing out, collecting, or managing physical keys.
• Time-controlled – Access during the booked period only (optionally with lead and wrap-up time).
• Traceable – Access events are logged.
• Self-service – Customers open the door independently via app or platform.

Provider	Short description
Tapkey	App-based opening; connect via “Connect to Tapkey” in Locaboo.
Comydo	Cloud access control with smartphone opening.
Salto KS	Salto cloud connection in Locaboo.
Evva Airkey	Smartphone-based access control.
Primion	Access control for larger facilities; file-based permission export.

Activation for many integrations is done via the Locaboo Marketplace ↗ and configured with your Locaboo contact.

Tapkey – setup (example)

1. Obtain hardware – At least one Tapkey lock or cylinder (e.g. via the Tapkey shop).
2. Commission the lock – Follow the instructions supplied with the hardware and create a Tapkey account. Important: The Tapkey account email must match your Locaboo account email.
3. Link Locaboo to Tapkey – In Locaboo: Settings → Integrations → under Tapkey, click Connect to Tapkey. Sign in on the Tapkey page; you are returned to Locaboo and the connection is active.
4. Lead and wrap-up times (optional) – After connecting, set check-in lead time and check-in wrap-up time. Example lead: 15 minutes, booking starts 11:00 → lock may open from 10:45. Example wrap-up: 15 minutes, booking ends 11:00 → lock until 11:15. If unset, the lock can only be opened during the exact booking window.
5. Assign locks to resources – Resources → edit the resource → General tab → Tapkey lock for this resource: select all locks required. One lock can be assigned to several resources.

From the customer perspective (opening via app or platform), the same booking times and permissions apply as described for the booking platform.

Comydo

1. Under Settings → Integrations, in the Comydo section, enable the integration via the checkbox.
2. Add devices – Add as many devices as needed; for each device enter the device ID (e.g. on the back of the Comydo scanner). Note: use the device ID, not the serial number.
3. Assign devices to resources – Define which device opens which room; a resource can be assigned to several Comydo devices.
4. Optional – resource list – In the resource list view, use the dot menu (right) to add the Digital locks column to the selected columns for easier overview.

Salto KS

Platform background: SALTO KS (vendor).

Prerequisites: active SALTO KS account and at least one registered digital lock (smart lock).

1. Connect – Settings → Integrations → under SALTO KS, click Connect to SALTO KS (or similar). Sign in on the SALTO KS platform and grant Locaboo access (Yes, allow). You are redirected back to Locaboo.
2. Resource mapping – Open Resource mapping, pick the matching lock per Locaboo resource and click Assign. Several locks per resource are allowed.
3. Lead and wrap-up times – Open the Lead and wrap-up times dialog and set values. Example: lead 1 hour, wrap-up 30 minutes, booking 14:00–16:00 → access from 13:00 to 16:30.

Evva Airkey

Prerequisites: active Evva Airkey account and at least one registered digital lock.

1. Connect – Settings → Integrations → Evva Airkey. Enter the API key from the Evva Airkey online admin under Settings and click Establish connection. A success message confirms the link.
2. Resource mapping – Same pattern as Salto KS: Resource mapping, select lock per resource, Assign; several locks per resource possible.
3. Lead and wrap-up times – Configure via the same type of dialog as for Salto KS.

Primion

1. Under Settings → Integrations, enable Primion (checkbox).
2. Per customer – In the customer record, on the Settings tab, enter the Primion ID where applicable.
3. Export – Export files with booking permissions are generated hourly and must be picked up via SFTP. Contact support@locaboo.com for file transfer setup and credentials.

---

WebUntis (for schools)

The integration imports timetables from WebUntis and maps WebUntis rooms to your Locaboo resources.

Prerequisites

• The Locaboo app has been enabled in your school’s WebUntis portal.
• You know your WebUntis tenant ID (from the WebUntis portal).
• The Locaboo resources to map are already created.

Steps in Locaboo

1. Start integration – Sign in → Settings → Integrations → WebUntis section → Configure integration (green button).
2. Tenant ID – On WebUntis mapping, under Link new integration, enter the tenant ID and click Search. The tenant ID uniquely identifies your school in WebUntis (ask your school if needed).
3. Link – When you see “integration found”, enter the school name and Link integration with organisation (green button). Details shown include tenant ID, who activated the integration, creation date.
4. Linked integration – Under Linked integrations, the entry appears; status may be assignment pending until rooms are mapped. Open Manage for details.
5. Management page – Under Integration status, see school name, tenant ID, and connection time. Actions may include Unlink integration, Reset integration (removes assignments and imported bookings—use with care), Sync rooms (reload rooms from WebUntis).
6. Room–resource assignment – For each WebUntis room, choose a Locaboo resource in the dropdown (hierarchical list: main and sub-resources). You can book the whole resource or a sub-resource. Choose Unassigned if the room is not used in Locaboo.
7. Finish – Save assignments & sync timetable – saves mappings and creates bookings for timetable slots of mapped resources.
8. Result – Slots appear in the Locaboo calendar as bookings.

Notes: Timetable imports are usually not manually editable. Enabling the Locaboo app in WebUntis is coordinated with school IT and Locaboo support.

---

Spielplus / DFBnet (for sports clubs)

Locaboo can import fixtures for league or friendly matches from Spielplus (DFBnet); match times can update automatically.

1. Venue numbers and resources

Venue numbers from the Spielplus export file (field venue no. / Spielstätten-Nr.) must be assigned to the Locaboo resources that should receive imports. Locaboo maps fixtures using this mapping.

2. Export match data from Spielplus

1. Sign in to SpielPLUS → menu Match results reporting → tab Club schedule is active.
2. Search – Matches must appear in the result list for the Export button to show (use filters, e.g. home/away).
3. Export → select the period → Continue – the export file downloads.

3. Import into Locaboo

Upload the file under Settings → Import / Export on the Spielplus tab. If kick-off times change, existing entries are updated and new ones imported; the whole resource is booked each time. Repeat export/import after changes in Spielplus.

First import: No automatic customer assignment—assign the customer in Locaboo manually. Later imports: Once customers are assigned, Locaboo can map via match ID (Spielplus); bookings may use colours from customer/customer group settings if configured.

4. Editing the export file (optional)

If you edit the CSV, keep the format: field separator TAB, text qualifier empty (e.g. OpenOffice with these settings). Otherwise re-import may fail.

---

SSO (single sign-on)

Locaboo supports SAML2 for single sign-on (e.g. Shibboleth). Users sign in with corporate credentials via your identity provider.

SAML2 / Shibboleth

1. On the identity provider, create an attribute locaboo_roles. It defines the role in Locaboo. Typical values: user, customer (all frontend types), plus other roles available in the manager. Optional: for customer, use locaboo_group with the customer group name.
2. In Locaboo: Settings → Integrations → SAML2 – single sign-on service – enter entity ID, single sign-on URL, optional single logout URL, x509 certificate (full PEM text) from the IdP.
3. Enable SAML2 sign-in (checkbox), save. Then download metadata.xml and finish IdP configuration. Optional: signed requests; paste the certificate text in Locaboo and use Locaboo’s public server certificate on the IdP side.
4. Test – After admin approval: SSO sign-in on the login page. Required claims: email, first name (first_name), last name (last_name).

Additional SAML2 behaviour:

• Users can be managed entirely in the SSO system.
• Profile (first name, last name, email) updates in Locaboo when it changes at the IdP.
• New users are created on first SSO login if they do not exist yet.
• Existing Locaboo users are matched and can keep using SSO.

Microsoft Azure AD

See SAML2 basics above. For Microsoft Entra ID (Azure AD) in short:

1. Sign in to Microsoft Azure → All services → Microsoft Entra ID (formerly Azure AD).
2. Enterprise applications → New application → Create your own application (name e.g. “Locaboo”) → Create.
3. Single sign-on → SAML → Get started. Upload Locaboo’s metadata.xml from Settings → Integrations → SSO section.
4. From Azure, copy into Locaboo: Login URL = single sign-on URL, Microsoft Entra identifier = entity ID, Logout URL = optional single logout URL.
5. Download the Base64 certificate and paste its content into Locaboo in the SSO section.
6. Under Attributes & claims, map first_name, last_name, locaboo_roles, and optionally locaboo_group. Example customer in group “intern”: first_name = Max, last_name = Doe, locaboo_roles = customer, locaboo_group = intern. If defaults are missing: Add new claim – e.g. givenname claim, set Name to first_name, leave Namespace empty, save; repeat for other attributes.
7. Assign Users and groups.

Technical questions: support@locaboo.com.

---

Outlook

The Outlook connection is in beta; not all features are final. Enablement is via support.

The integration connects Microsoft Outlook to Locaboo and syncs bookings / appointments toward Outlook calendars (mapped to resources).

After enablement:

1. Settings → Integrations → Outlook → Connect Outlook – complete Microsoft sign-in and grant access to Outlook data.
2. Map calendars – Assign Locaboo resources to the desired Outlook calendars.
3. Sync – New bookings for the mapped resource are pushed to the Outlook calendar (Locaboo → Outlook only; changes in Outlook are not written back to Locaboo).
4. Disconnect – Disconnect stops the connection; no further sync.

Notes: The sign-in popup may show the app as not verified temporarily (Microsoft verification in progress). Only Locaboo → Outlook sync is supported.

---

Accounting and financial systems (HKR systems)

Locaboo offers interfaces to common accounting systems. The connection is GoBD-compliant and takes into account municipal VAT rules (Section 2b German VAT Act). A certification for cash management or cash audits is not required.

Typical workflow (with Locaboo):

1. Align master data in Locaboo and the target system (cost centres, general ledger accounts, tax keys).
2. Configure the integration under Settings > Integrations or the finance interfaces add-on as agreed.
3. Run a test export / validation, then go live.

Details: Finance interfaces add-on and your Locaboo contact.

---

API

External systems access Locaboo via the REST API.

API reference

Public endpoints and usage: app.locaboo.com/api-reference.html

Secret key

1. In Locaboo, click your name (top right) → Account.
2. In the right column, open API credentials – this shows your secret key for the API.
3. Use the key as described in the API reference.

API questions: support@locaboo.com

---

Further integrations

Integration	In brief
iCalendar export	Enable the secure iCal connection under Settings > Calendar.
CSV import/export	Import / Export – customer data via CSV; use sample files.

SPF

Locaboo sends email via a specialised provider (hosted in Germany). To send from your own domain, you need an SPF DNS record.

Setup: Contact support@locaboo.com for the correct SPF values for your domain.

Alternative: Sending via your own SMTP server is possible (coordinate with Locaboo).

2D maps

2D maps embed interactive building or site plans in the booking platform (orientation, routes, possibly floors). Exact setup (file formats, hotspots, resource mapping) depends on your Locaboo configuration and is guided in Integrations and/or platform / widget settings.

Note: For implementation details, work with your Locaboo contact or support if your UI differs.