Resivo integration: introduction and functional background
What is Resivo?
Resivo is a cloud-based access-control system by dormakaba. The platform manages digital keys and door opening for residents, managers and visitors, with separate documentation per audience:
- Residents & tenants — the resivo home app for activating digital keys and managing housemates or temporary access.
- Managers (facility management) — the resivo Utility app for tenant check-in/check-out processes.
- Developers — the Resivo API for contracts, billing and access management.
i-Reserve connects to the Resivo API and uses one capability: visitor management with remote door opening. A booking automatically grants the visitor access to the right door(s) for the duration of the booking; on cancellation that access is revoked. Resivo is the successor to the former Exivo integration.
Terminology: Exivo → Resivo
| Exivo / Dormakaba | Resivo |
|---|---|
| Customer / Site | Site Owner (organisation) → Site |
| Visit | Remote Access Authorization Set |
| Component | Component (same concept: door / access point) |
In the i-Reserve configuration we use Resivo’s own terminology (Site Owner instead of “customer”).
Authentication
The integration uses OAuth 2.0 client credentials at organisation level. One credential (client id + client secret) of a Site Owner grants access to all of its sites. i-Reserve fetches an access token automatically and reuses it while it is valid.
What happens on a status change
The integration reacts to booking status changes:
- When a booking reaches a trigger status, i-Reserve creates a Remote Access Authorization Set: the mapped door(s), valid from (start − time before) until the booking end time.
- Resivo itself sends an email/text to the visitor with a door link to open the door remotely.
- The id of the created authorisation is stored in a chosen booking field — required to revoke the access later.
- When the booking reaches a revoke status (e.g. cancelled), i-Reserve revokes the access again.
Mapping by name
Linking i-Reserve objects to Resivo doors (components) is done by name, not by id. A component’s display name (e.g. “Digital cylinder – double”) is unique per site, while the id can change on a site migration. On every trigger, i-Reserve resolves the current ids from the selected names.
Phone numbers (SMS)
For SMS, Resivo only accepts mobile numbers in E.164 format (+31612345678). i-Reserve normalises 00… to +… and strips spaces. A number without a country code (e.g. 06… or a landline) is skipped: only the SMS is dropped, while access and email keep working.
Limitations (current state)
- Door link not via the API — the portal link Resivo uses is not returned in the API response. i-Reserve therefore cannot pre-build that link in its own mail template; Resivo sends the link via its own email/SMS.
- Mail language via the site — the language of Resivo’s messages comes from the site’s
defaultLocale(set once in the Resivo portal). - Notifications via Resivo only — the email to the visitor is sent exclusively by Resivo; i-Reserve does not send its own mail for this. The text of these Resivo emails cannot be customised.
- Time zones — valid-from/to are sent in UTC. The i-Reserve server must have the correct time zone as default, otherwise the times are off.
