Create a recording for the call
Create a recording for the call
Path parameters
The SID of the Account that will create the resource.
The SID of the Call to associate the resource with.
Response
OK
The SID of the Account that created the Recording resource.
The API version used to make the recording.
The SID of the Call the Recording resource is associated with.
The Conference SID that identifies the conference associated with the recording, if a conference recording.
The date and time in GMT that the resource was created specified in RFC 2822 format.
The date and time in GMT that the resource was last updated, specified in RFC 2822 format.
The start time of the recording in GMT and in RFC 2822 format.
The length of the recording in seconds.
The unique string that that we created to identify the Recording resource.
The one-time cost of creating the recording in the price_unit currency.
The URI of the resource, relative to https://api.twilio.com.
The currency used in the price property. Example: USD.
The status of the recording. Can be: processing, completed and absent. For more detailed statuses on in-progress recordings, check out how to Update a Recording Resource.
The number of channels in the final recording file. Can be: 1, or 2. Separating a two leg call into two separate channels of the recording file is supported in Dial and Outbound Rest API record options.
How the recording was created. Can be: DialVerb, Conference, OutboundAPI, Trunking, RecordVerb, StartCallRecordingAPI, and StartConferenceRecordingAPI.
The error code that describes why the recording is absent. The error code is described in our Error Dictionary. This value is null if the recording status is not absent.
The recorded track. Can be: inbound, outbound, or both.