Get Current User in Users (Okta )

What this operation does

Get Current User

• GETReads dataokta.local/api/v1/users/me

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Users (Okta ) operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Users (Okta ) operations

• Create User in GroupPOST · changes data
• Clear User SessionsDELETE · changes data
• Suspend UserPOST · changes data
• Activate UserPOST · changes data
• Set Recovery CredentialPUT · changes data
• Unsuspend UserPOST · changes data
• Deactivate UserPOST · changes data
• Reset FactorsPOST · changes data

All 19 Users (Okta ) operations

Questions

Can HumDay get current user in Users (Okta )?

Yes. This operation is published in Users (Okta )'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 Users (Okta ) account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Users (Okta ).

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 Users (Okta ) account.

Where this came from

Read from a published API description for Users (Okta ) at www.postman.com/collections/1755573c5cf5fbf7968b. The description above is the provider’s own wording, not ours. Last published 2021-07-05.