I’m experiencing an issue with the Nuki API regarding data synchronization for user names. After updating user names directly in the Nuki Web interface to match a specific naming convention (e.g., family names in uppercase and accents preserved), I noticed that the API does not immediately reflect these changes in the expected format.
Specifically:
Last names appear in mixed case instead of uppercase in API responses, even though they are displayed correctly in uppercase in Nuki Web.
I’ve verified with the support team that API data should update instantly upon changes, but this inconsistency persists.
This issue is impacting my ability to automate access management by matching API data with a Google Sheet, which requires consistent naming formats.
Could you please advise on this situation? Is there a known delay in the API updating name formatting, or any workaround to ensure API data mirrors the naming conventions applied in Nuki Web?
name (device name displayed in “Devices” section in Nuki Web)
config name (the name displayed when you click on “Manage Device” button in “Devices” section in Nuki Web)
Since you are relying on the names for automation, I would advise you to rely on the config name.
When the config name is changed, you would need to update the configuration of the device for it to reflect.
This can be done in 2 ways:
Click on “Update now” button for the device from Nuki Web
POST /smartlock/{smartlockId}/config to update the config via the API immediately
A daily sync also updates the config details, but this happens only once a day, in order to not drain the battery of the device.
Thus, you can trigger this instantly using the above two update methods or wait for a day for the details to be updated. I can validate that it works correctly as I tested it with our smart locks.
Thank you for your response. I’d like to clarify that the field that is not updating as expected is actually the name field returned by the API when querying user authorizations, specifically via the endpoint https://api.nuki.io/smartlock/{smartLockID}/auth.
In Nuki Web, when viewing a user’s information, the username field shows both the first and last names in uppercase. However, when retrieving this same name data via the API, it does not reflect this capitalization and instead retains a different formatting.
I wanted to ensure you are aware that this discrepancy is in the user authorization details rather than the device configuration name. Could you advise if there is a way to ensure that the name field updates to reflect changes in Nuki Web? Or if this field can be standardized in the API response to match the username format visible in the Nuki Web interface?
We tested this by updating the user / authorization name with capitalization and there are no issues. The case is returned exactly the way it is updated. Hence, this is not an issue with the API. Hence, for more support, please contact our Support team.
Thank you for your response. I’ve attached two screenshots to illustrate the issue clearly. In the Nuki Web interface, names appear as expected in uppercase (matching the updated format in our settings). However, in the API response at the /smartlock/{smartLockID}/auth endpoint, the name field does not reflect these updates, showing names in lowercase.
Additionally, the Nuki support team advised me to reach out to the developer forum for further assistance on this issue. Any guidance on a resolution would be much appreciated.
Thank you for the additional info, the issue is more clearer now.
An account user is created, and any changes to the names are updated to the account user only, and not all the user permissions associated with the account user. This is not just in the API, but also on the Nuki Web UI (name is not displayed).
For eg. if an account user is created with “Firstname Lastname”, and assigned to a smart lock, then smart lock auth has the name “Firstname Lastname”. Now, if the account user name is updated to “Firstname LASTNAME”, the smart lock auth still remains “Firstname Lastname”. If you want this to be updated, please delete the auth and create it again.
A workaround for you could be to create the account users with the correct name, and capitalisation, and then assign it to a device as user permission. For the requirement of updating user name afterwards, please create a feature request here: Feature requests - Nuki Developers
