Streams one of a user's hold messages, so a browser or an <audio> element can play it. Call it with a bearer token or session cookie, or with no token through the signed file-access-url that every read of the file returns. With a token, any user can play its own hold messages, and Office Manager, Site Manager, Call Center Supervisor, Route Manager, Reseller, and Super User the hold messages of users in their domain or territory.
Request
Authorization
Bearer Token
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
or
Path Params
Query Params
Responses
🟢200OK
audio/wav
The hold message's bytes. The body is the file: audio/wav, or audio/aac or audio/ogg with convert. Shared caches never store the response. It is binary, so there is no example.