Retrieve a user in Vonage Conversation

What this operation does

Retrieve a user

• GETReads data · userapi.nexmo.com/users/{user_id}

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 Vonage Conversation 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 Vonage Conversation operations

• Create a userPOST · changes data
• Create an eventPOST · changes data
• Delete a userDELETE · changes data
• Update a userPUT · changes data
• Create a conversationPOST · changes data
• Delete an eventDELETE · changes data
• Record a conversationPUT · changes data
• Create a memberPOST · changes data

All 19 Vonage Conversation operations

Questions

Can HumDay retrieve a user in Vonage Conversation?

Yes. This operation is published in Vonage Conversation'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 Vonage Conversation account?

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

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 Vonage Conversation account.

Where this came from

Read from a published API description for Vonage Conversation at raw.githubusercontent.com/nexmo/api-specification/master/definitions/conversation.yml. The description above is the provider’s own wording, not ours. Last published 2023-03-24.