Setting up the Salto KS integration: steps on the Salto and i-Reserve side
The Salto KS integration needs configuration on two sides: first the Salto installation (Site + IQ + locks + account), then the integration in i-Reserve, including activating the IQ PIN.
1. On the Salto side
- Make sure a Site exists and note the Site UID (e.g.
NL6254340082). - Make sure the IQ online gateway is linked to the site and online; note the IQ id.
- Make sure the locks to be operated are registered in the site and reachable via the IQ.
- Create/use a Salto KS account (username + password) with sufficient rights on the site.
The OAuth client credentials for Salto KS are managed at platform level by i-Reserve; you provide the account.
2. On the i-Reserve side — Authentication tab
| Field | What to enter |
|---|---|
| Environment | Acceptance (testing) or Production (live). Required. |
| Site UID | The human-readable site code from Salto (e.g. NL6254340082). Required. |
| Site ID | The internal site id (UUID). Click Resolve site ID to fetch it automatically from the Site UID. Read-only. |
| Username | The username of the Salto KS account. Required. |
| Password | The password of the Salto KS account. Required. |
Click Test / request access to fetch a token and verify the connection.
2.1 IQ OTP setup (activate the PIN)
In the IQ OTP setup block you activate the IQ gateway with a PIN. This is required before locks can be opened.
- Enter the IQ id (UUID of the IQ gateway).
- Click GET PIN to fetch the current PIN from the IQ (appears in current pin).
- Enter the desired 4-digit PIN in new pin.
- Click Set PIN: i-Reserve sets the new PIN on the IQ (signed with an OTP based on the current PIN + the IQ secret).
- On success the status changes to “IQ is activated”. From now on i-Reserve can sign valid open commands.
3. Details tab
| Field | What it does |
|---|---|
| Lock may open from status | The booking status(es) at which opening the lock is allowed. Multiple selection. |
| Time before (minutes) | Number of minutes before the start time that opening is already allowed (0–1440). |
| Save last open action in field | Booking field that records the open timestamp. Optional. |
| Status after opening (check-in) | The booking is automatically moved to this status after a successful opening. Optional. |
3.1 Mapping: object → lock
On the Mapping tab you link each i-Reserve object (product) to a lock. Choose the product on the left and the lock on the right from the dropdown; populate that list with the GET locks button (fetches the site’s locks). An object without its own mapping can fall back to a default (wildcard) lock.
Objects and sub-objects. The object dropdown on the left now lists both main objects and their sub-objects. This lets you map at the level of a specific sub-object (for example one studio within a parent object), not just the main object. A booking on a sub-object carries that sub-object, so the most specific mapping applies. Existing main-object mappings keep working.
4. Activate
Save and set the integration to active. Test by moving a booking to the configured status and running the open action; verify the lock opens and (if configured) the open time and the check-in status are updated.
