Update validated user list in Example Rudder
A documented Example Rudder operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Update validated user list
- POSTChanges data · 🧩 Change requests
rudder.example.local/validatedUsers
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 Example Rudder operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Example Rudder operations
- Create one or several new nodesPUT · changes data
- Create a new parameterPUT · changes data
- Remove an user from validated user listDELETE · changes data
- Create a rulePUT · changes data
- Create a groupPUT · changes data
- Create a secretPUT · changes data
- Create a directivePUT · changes data
- Create techniquePUT · changes data
Questions
- Can HumDay update validated user list in Example Rudder?
- Yes. This operation is published in Example Rudder's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Example Rudder data?
- Yes — this is a POST operation, so it changes something in Example Rudder. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- 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 Example Rudder account.
Where this came from
Read from a published API description for Example Rudder at docs.rudder.io/api/openapi.yml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.