Get user's ZAK in Zoom
A documented Zoom 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 user's ZAK
- GETReads data · Users
api.zoom.us/users/me/zak
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 Zoom 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 Zoom operations
- Create a channelPOST · changes data
- Send a chat messagePOST · changes data
- Create usersPOST · changes data
- Add a user's TSP accountPOST · changes data
- Update a user's emailPUT · changes data
- Upload a user's profile picturePOST · changes data
- Create a meetingPOST · changes data
- Create a blocked listPOST · changes data
Questions
- Can HumDay get user's zak in Zoom?
- Yes. This operation is published in Zoom'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 Zoom account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Zoom.
- 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 Zoom account.
Where this came from
Read from a published API description for Zoom at marketplace.zoom.us/docs/api-reference/zoom-api/Zoom%20API.oas2.json. The description above is the provider’s own wording, not ours. Last published 2021-07-02.