Recording status callback
Payload sent by SignalWire to your `RecordingStatusCallback` URL when a recording status event occurs.
Recordings are not always available immediately — especially at high call volumes. This callback lets
your app react as soon as a recording is ready, whether that means uploading it to external storage,
sending it via email, or forwarding the URL via SMS.
Configure `RecordingStatusCallback` when
[creating a call via the API](/docs/compatibility-api/rest/calls/create-a-call) or when using
[Dial](/docs/compatibility-api/cxml/reference/voice/dial),
[Conference](/docs/compatibility-api/cxml/reference/voice/conference), or
[Record](/docs/compatibility-api/cxml/reference/voice/record).
Use `RecordingStatusCallbackEvent` to request callbacks for specific events. If omitted, only the
`completed` event is sent. Possible values: `in-progress`, `completed`, `absent`.
| Status | Description |
|--------|-------------|
| `in-progress` | The recording has begun. |
| `completed` | The file is available for access. |
| `absent` | The recording was too short or the call was silent — no audio was detected. |
Payload
The payload of this webhook request is an object.
AccountSid
The unique ID of the project this call is associated with.
CallSid
A unique identifier for the call. May be used to later retrieve this call from the REST API.
RecordingSid
The unique identifier for the recording.
RecordingUrl
The URL for the audio recording.
RecordingStatus
The status of the recording.
- `in-progress`: Recording has begun.
- `completed`: File is available.
- `absent`: Recording was too short or no audio was detected.
Allowed values:
RecordingDuration
The duration, in seconds, of the recording.
RecordingChannels
The number of channels in the recording.
RecordingSource
The type of call that initiated the recording.
Response
200
Webhook received
