Update a user's roles in Agco ATS AGCO
A documented Agco ATS AGCO 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 a user's roles
- PUTChanges data · UserPermissions
secure.agco-ats.com/api/v2/Users/{id}/Roles
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 Agco ATS AGCO 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 Agco ATS AGCO operations
- Create the metadata for a file before uploadingPOST · changes data
- Create a userPOST · changes data
- Sends an email messagePOST · changes data
- Adds a User RolePOST · changes data
- Add a new Update GroupPOST · changes data
- Upload the contents of a filePUT · changes data
- Add a new Package Type ID to Bundle RelationshipPOST · changes data
- Create the metadata for a file before uploadingPOST · changes data
Questions
- Can HumDay update a user's roles in Agco ATS AGCO?
- Yes. This operation is published in Agco ATS AGCO'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 Agco ATS AGCO data?
- Yes — this is a PUT operation, so it changes something in Agco ATS AGCO. 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 Agco ATS AGCO account.
Where this came from
Read from a published API description for Agco ATS AGCO at secure.agco-ats.com:443/swagger/docs/v1. The description above is the provider’s own wording, not ours. Last published 2023-03-06.