Play an audio file into a call in Vonage Voice
A documented Vonage Voice 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
Play an audio file into a call
- PUTChanges data · Stream Audio
api.nexmo.com/{uuid}/stream
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 Voice 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 Voice operations
- Create an outbound callPOST · changes data
- Stop playing an audio file into a callDELETE · changes data
- Modify an in progress callPUT · changes data
- Play DTMF tones into a callPUT · changes data
- Stop text to speech in a callDELETE · changes data
- Play text to speech into a callPUT · changes data
- Get details of your callsGET · reads data
- Get detail of a specific callGET · reads data
Questions
- Can HumDay play an audio file into a call in Vonage Voice?
- Yes. This operation is published in Vonage Voice'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 Voice data?
- Yes — this is a PUT operation, so it changes something in Vonage Voice. 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 Voice account.
Where this came from
Read from a published API description for Vonage Voice at raw.githubusercontent.com/nexmo/api-specification/master/definitions/voice.yml. The description above is the provider’s own wording, not ours. Last published 2023-03-24.