Transfer number in Vonage Subaccounts
A documented Vonage Subaccounts operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Transfer number
- POSTChanges data · Transfers
api.nexmo.com/{api_key}/transfer-number
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 Vonage Subaccounts operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Vonage Subaccounts operations
- Create subaccountPOST · changes data
- Transfer creditPOST · changes data
- Transfer balancePOST · changes data
- Modify a subaccountPATCH · changes data
- Retrieve list of subaccountsGET · reads data
- Retrieve list of credit transfersGET · reads data
- Retrieve list of balance transfersGET · reads data
- Retrieve a subaccountGET · reads data
Questions
- Can HumDay transfer number in Vonage Subaccounts?
- Yes. This operation is published in Vonage Subaccounts's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Vonage Subaccounts data?
- Yes — this is a POST operation, so it changes something in Vonage Subaccounts. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- 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 Subaccounts account.
Where this came from
Read from a published API description for Vonage Subaccounts at raw.githubusercontent.com/nexmo/api-specification/master/definitions/subaccounts.yml. The description above is the provider’s own wording, not ours. Last published 2023-03-24.