Instruction
Difficulty level:
Implementing the Resivo integration: test and production checklist
Practical implementation guide for the Resivo integration (visitor management with remote door opening), with a checklist for test and production. The steps describe the order; then use the per-environment checklists.
Things to watch
- One credential with scope Customer covers all of the organisation’s sites; choose Site only for deliberate restriction.
- The components (doors) must have a unique display name in Resivo — those names are what you select in the mapping.
- The booking field for the authorisation id is required to revoke access.
- The server time zone must be correct (valid-from/to are sent in UTC).
Checklist — test environment
- ☐ In the Resivo portal: Customer ID (= Site Owner ID) noted.
- ☐ Credential generated (scope Customer); Client ID and Secret copied immediately.
- ☐ Site ID noted if needed (for mapping/single-site restriction).
- ☐ Components (doors) in Resivo given unique display names.
- ☐ i-Reserve Auth tab filled (Site Owner ID, Client ID, Client secret, optional Site ID); connection tested.
- ☐ Details tab: trigger and revoke statuses, time before, booking field and default language set.
- ☐ Mapping: objects linked to the right door(s).
- ☐ Integration set to active.
- ☐ End-to-end tested: booking → trigger status → visitor receives door link; then revoke status → access revoked.
Checklist — production environment
- ☐ Production credentials generated (own Client ID/Secret); Site Owner ID verified.
- ☐ Site
defaultLocaleset correctly in the Resivo portal (determines the language of Resivo’s messages). - ☐ Real doors mapped correctly to the production objects.
- ☐ Trigger/revoke statuses aligned with the real booking flow.
- ☐ Duplicate-notification alignment: own booking email vs. Resivo email/SMS.
- ☐ First live booking verified (access created + revoked).
- ☐ Rollback known: setting the integration inactive stops new authorisations.
In the Resivo portal open the API screen, note the Customer ID (= Site Owner ID) and generate a credential with scope Customer; copy the Client ID and Secret immediately.
In Administration > Integrations add a Resivo integration and fill the Auth tab (Site Owner ID, Client ID, Client secret, optional Site ID); test the connection.
On the Details tab set the trigger and revoke statuses, the time before, the booking field for the authorisation id and the default language.
On the Mapping tab link each object to the right Resivo component(s); the choice is by display name.
Set the integration active, move a test booking to a trigger status and check the door link; then test revocation via a revoke status.
