Before storing anything, QuietStay signs in to your provider with the key you pasted. This message means that call came back refused, so the connection was not created and nothing was kept.
Check these in order
- The whole key. Copy it again from the provider and paste it in one go. A missing last character looks exactly like a wrong key.
- The right provider. A Lodgify key sent to Hostaway is refused. Check the Provider box matches where the key came from.
- Hostaway pairs. Hostaway needs the account ID and the key together, both from Settings, then Hostaway API. A key with the wrong account ID is refused.
- The key is still live. Keys that have been revoked, rotated or expired are refused. Generate a new one.
- Permissions. The key must be allowed to read reservations and listings. A read-only key made for something else may not be.
Then try again
Paste the new key and press Connect. Nothing was stored on the failed attempt, so there is nothing to undo first. If a connection for that provider already exists, press Disconnect on it before connecting again.
For Nuki
The Nuki token is checked the same way, against your Nuki Web account. Generate it under Nuki Web, then API, and make sure it is a token for the account that owns the locks.
If it still will not connect
Reply to any email from QuietStay saying which provider you are connecting and when you generated the key. Never send the key itself — we cannot use it and it does not belong in an email.