Call Recording
The call's recording, as audio the ticket's player can play.
⛔THE ONE WAY A RECORDING REACHES A SCREEN (ISS-1675). Mark, on the Desk: "I'm unable to play or listen to the call recordings ... All the recordings ... Open tickets and resolved tickets." The ticket used to put recording_url straight into <audio src>, and that is a Plivo URL our account's basic auth guards, or a bucket link signed for an endpoint the API reaches and a browser may not. Read here, behind the same cs:voice grant that shows the call at all, and served to a signed-in fetch (fetchObjectUrl), it plays whichever of the two the row holds.
⛔HOLDS NO POOL CONNECTION WHILE THE AUDIO IS FETCHED (ISS-1761). The read goes to Plivo (up to 60 s) or the bucket; with get_connection the slot was held for all of it, p95 60 s and 2.9 s of pool wait for everyone else. The row is one statement, so it takes a BriefConnection.
Request
- Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
- URL: https://api.pigeonly.com/api/voice/calls/{call_uuid}/recording
- Auth: none declared
Path parameters
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.