Gets the settings of a folder or meter in smart me
A documented smart me operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Gets the settings of a folder or meter
- GETReads data · FolderSettings
smart-me.com/api/folder/settings/{id}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which smart me operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other smart me operations
- Creates and updates the folder menu itemsPOST · changes data
- Creates a new registration for the realtime APIPOST · changes data
- Beta: Virtual Meter API: Activates a MeterPOST · changes data
- Deletes a user to folder assignementDELETE · changes data
- Assign a user to a folderPOST · changes data
- M-BUS API: Adds data of a M-BUS Meter to the smart-me CloudPOST · changes data
- Triggers user account deletionDELETE · changes data
- Creates or updates a Device or updates it's valuesPOST · changes data
Questions
- Can HumDay gets the settings of a folder or meter in smart me?
- Yes. This operation is published in smart me's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my smart me account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in smart me.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your smart me account.
Where this came from
Read from a published API description for smart me at smart-me.com/swagger/docs/v1. The description above is the provider’s own wording, not ours. Last published 2023-03-06.