Create a Recording
Create a recording.
Permissions
The API token used to authenticate must have the following scope(s) enabled to make a successful request: Voice.
Create a recording.
The API token used to authenticate must have the following scope(s) enabled to make a successful request: Voice.
The number of channels in the recording. Can be mono (both legs of call recorded under one channel into one recording file) or dual (each leg of call recorded in separate channels into one recording file). Default is mono.
The URL to request to when recording is available. See the Recording status callback webhook for the payload your URL will receive.
The different recording statuses. To specify multiple events, separate with a space. Valid values: completed, in-progress, absent. Default is completed.
Whether the request to RecordingStatusCallback URL is a GET or a POST. Default is POST.
Specifies whether to record the inbound audio to SignalWire from the called party or the outbound audio from SignalWire to the called party or both the inbound and outbound audio. Default is both.
Whether leading and trailing silence is trimmed from a recording. Default is do-not-trim.
The number of channels in a recording (singular key). Returns ‘1’ for mono or ‘2’ for stereo.
SignalWire Basic Authentication using Project ID and API Token.
The client sends HTTP requests with the Authorization header containing the word Basic followed by a space and a base64-encoded string of project_id:token. The project ID will be used as the username and the API token as the password.
Example: