Returns latest scanner version in Rumble (deprecated)
A documented Rumble (deprecated) 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
Returns latest scanner version
- GETReads data · Public
console.rumble.run/releases/scanner/version
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 Rumble (deprecated) 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 Rumble (deprecated) operations
- Create a new user accountPUT · changes data
- Create a new user account and send an email invitePUT · changes data
- Sends the user a password reset emailPATCH · changes data
- Create a new scan templatePOST · changes data
- Create a new sitePUT · changes data
- Create a new keyPUT · changes data
- Create a new organizationPUT · changes data
- Create a new groupPOST · changes data
Questions
- Can HumDay returns latest scanner version in Rumble (deprecated)?
- Yes. This operation is published in Rumble (deprecated)'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 Rumble (deprecated) account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Rumble (deprecated).
- 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 Rumble (deprecated) account.
Where this came from
Read from a published API description for Rumble (deprecated) at raw.githubusercontent.com/RumbleDiscovery/rumble-api/main/rumble-api.yml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.