Request customer information for user in DRACOON
A documented DRACOON 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
Request customer information for user
- GETReads data · user
/v4/user/account/customer
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 DRACOON 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 DRACOON operations
- Create new userPOST · changes data
- Create new Upload SharePOST · changes data
- Set file keys for a list of users and filesPOST · changes data
- Create new file upload channelPOST · changes data
- Create new user groupPOST · changes data
- Updates a list of file’s metadataPUT · changes data
- Create new folderPOST · changes data
- Mark or unmark a list of nodes (room, folder or file) as favoritePUT · changes data
Questions
- Can HumDay request customer information for user in DRACOON?
- Yes. This operation is published in DRACOON'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 DRACOON account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in DRACOON.
- 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 DRACOON account.
Where this came from
Read from a published API description for DRACOON at dracoon.team/api/spec_v4/. The description above is the provider’s own wording, not ours. Last published 2023-03-06.