Get specific account in N Auth nextAuth
A documented N Auth nextAuth 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
Get specific account
- GETReads data · Accounts
api.nextauth.com/servers/{serverid}/accounts/{accountid}/
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 N Auth nextAuth 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 N Auth nextAuth operations
- Create a new API keyPOST · changes data
- Create a new serverPOST · changes data
- Get or create a role for a specific userPOST · changes data
- Delete a specific userDELETE · changes data
- Delete all global attributesDELETE · changes data
- Set all global attributesPOST · changes data
- Update specified global attributesPUT · changes data
- Delete all accounts of a specific userDELETE · changes data
Questions
- Can HumDay get specific account in N Auth nextAuth?
- Yes. This operation is published in N Auth nextAuth'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 N Auth nextAuth account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in N Auth nextAuth.
- 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 N Auth nextAuth account.
Where this came from
Read from a published API description for N Auth nextAuth at api.docs.nextauth.com/api/swagger.json. The description above is the provider’s own wording, not ours. Last published 2021-04-07.