Developer
Instruction
Difficulty level: Intermediate

Practical implementation guide for the Salto KS integration (access control with IQ gateway and locks), with a checklist for test and production. The steps describe the order; then use the per-environment checklists.

Things to watch

  • The IQ gateway must be online and activated with a PIN ("IQ is activated").
  • The PIN + the IQ secret form the time-based OTP; do not change the PIN outside i-Reserve without re-activating.
  • Test fully in acceptance first; production has its own account, site and IQ.
  • The server time zone must be correct (OTP and time window use UTC).

Checklist — test environment (acceptance)

  • ☐ Salto site exists; Site UID noted.
  • ☐ IQ online gateway linked and online; IQ id noted.
  • ☐ Locks registered in the site and reachable via the IQ.
  • ☐ Salto KS account (username + password) with rights on the site.
  • ☐ i-Reserve Auth tab: environment = Acceptance, Site UID filled, Site ID fetched via "Resolve site ID", account filled; connection tested.
  • ☐ IQ OTP setup: IQ id filled, GET PIN, new PIN set via Set PIN; status = "IQ is activated".
  • ☐ Details tab: "lock may open from status", time before, open-action field and check-in status set.
  • ☐ Mapping: products linked to the right locks (GET locks).
  • ☐ Open link {OPENLOCKLINK} included in an e-mail or SMS template the customer receives in time.
  • ☐ Integration set to active.
  • ☐ Only for locks with a keypad: PIN when possible set to Yes, booking field for the PIN chosen, {LOCKPIN} in the confirmation, and the PIN of the test booking opens the lock.
  • ☐ End-to-end tested: booking in an allowed status → Lock check from the booking: all criteria green → open the link from the template → Open door → lock opens; open time and check-in status verified.

Checklist — production environment

  • ☐ Environment set to Production; production account, production site (Site UID) and production IQ used.
  • ☐ IQ online in production and activated with a PIN ("IQ is activated").
  • ☐ Real locks mapped correctly to the production products.
  • ☐ Statuses (opening allowed + check-in) aligned with the real booking flow.
  • ☐ Production template with {OPENLOCKLINK} active and sent at the right moment.
  • ☐ First live opening verified (lock opens + open time/check-in updated).
  • ☐ Rollback known: setting the integration inactive stops new open actions.

Make sure the Site exists (note the Site UID), the IQ gateway is online (note the IQ id) and the locks are registered; arrange a Salto KS account with rights on the site.

In Administration > Integrations add a Salto KS integration; choose the environment, fill Site UID + account, fetch the Site ID with Resolve site ID and test the connection.

In the IQ OTP setup block enter the IQ id, click GET PIN, set a new 4-digit PIN via Set PIN and verify the status shows "IQ is activated".

On the Details tab set "lock may open from status", time before, open-action field and check-in status; in the mapping link each product to the right lock (GET locks).

Include the variable {OPENLOCKLINK} in an e-mail or SMS template the customer receives before the start (for example the confirmation or a reminder). The integration sends nothing by itself: without this link the customer cannot open the lock.

Set the integration active and move a test booking to an allowed status. In the action block, use Salto KS lock to verify all criteria are green (see the article Lock check from the booking). Then open the link from the template and press Open door; verify the lock opens and the open time/check-in are updated.