How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SignalWire Recordings API

Manage call recordings.

SignalWire Recordings API is one of 80 APIs that SignalWire publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Recordings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 8 operations across 6 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://{space_name}.signalwire.com/api/laml/2010-04-01, https://{space_name}.signalwire.com.

8 operations 6 paths 24 schemas 2 DELETE4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://{space_name}.signalwire.com
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

SignalWire Recordings API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (SignalWireBasicAuth). It accepts HTTP bearer tokens (SignalWireBearerAuth). By default, every request must be authenticated.

  • SignalWireBasicAuth — SignalWire Basic Authentication using Project ID and API Token. The client sends HTTP requests with the Authorization header containing the word Basic followed…
  • SignalWireBearerAuth — SignalWire Bearer Token Authentication for subscriber endpoints. The client sends HTTP requests with the Authorization header containing the word Bearer follow…

Paths & Operations 8

Across 6 paths, the API surfaces 8 operations — 2 DELETE, 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Recordings 8

Manage call recordings.

POST
/Accounts/{AccountSid}/Calls/{CallSid}/Recordings
Create a Recording
create_recording 2 params body → 200400401404422503
POST
/Accounts/{AccountSid}/Calls/{CallSid}/Recordings/{Sid}
Update a Recording
update_recording 3 params body → 200400401404422503
GET
/Accounts/{AccountSid}/Recordings
List all Recordings
list_recordings 9 params → 200400401422
GET
/Accounts/{AccountSid}/Recordings/{Sid}
Retrieve a Recording
retrieve_recording 2 params → 200400401404
DELETE
/Accounts/{AccountSid}/Recordings/{Sid}
Delete a Recording.
delete_recording 2 params → 204400401404422
GET
/api/relay/rest/recordings
List recordings
list_call_recordings → 200401404422500
GET
/api/relay/rest/recordings/{id}
Get recording
get_call_recording 1 param → 200401404422500
DELETE
/api/relay/rest/recordings/{id}
Delete recording
delete_call_recording 1 param → 204401404422500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are Recording (21 properties), RecordingResponse (21 properties), CallRecordingResponse (21 properties), PstnRecording (15 properties). Each schema is shown below with its type and property counts.

Recording
object
Recording model.
21 properties 21 required
uuid
string
Universal Unique Identifier.
RecordingListResponse
object
Response containing a list of recordings.
7 properties 7 required
RecordingSubresourceUris
object
Recording subresource URIs.
1 property 1 required
RecordingSource
string
Recording source.
CreateCallRecordingRequest
object
Request body for creating a call recording.
6 properties
RecordingStatusCallbackPayload
object
8 properties 8 required
RecordingResponse
object
Response containing a single recording.
21 properties 21 required
CompatibilityErrorResponse
object
Error response model.
4 properties 4 required
CallRecordingResponse
object
Response containing a single call recording.
21 properties 21 required
UpdateCallRecordingRequest
object
Request body for updating a call recording.
2 properties 1 required
RecordingStatus
string
Recording status.
Recording_2
Recording model. A recording is associated with exactly one source type (PSTN, SIP, WebRTC, or Relay conference).
Types.StatusCodes.StatusCode401
object
Access is unauthorized.
1 property 1 required
PstnRecording
object
Recording from a PSTN call leg.
15 properties 12 required
ConferenceRecording
object
Recording from a Relay conference.
14 properties 12 required
Types.StatusCodes.StatusCode404
object
The server cannot find the requested resource.
1 property 1 required
Types.StatusCodes.ValidationError
object
The request failed validation. See errors for details.
1 property 1 required
RecordingListResponse_2
object
Response containing a list of recordings.
2 properties 2 required
Types.StatusCodes.SpaceApiErrorItem
object
Details about a specific validation error.
4 properties 4 required
Types.StatusCodes.StatusCode500
object
An internal server error occurred.
1 property 1 required
SipRecording
object
Recording from a SIP call leg.
15 properties 12 required
WebRtcRecording
object
Recording from a WebRTC call leg.
15 properties 12 required
PaginationLinks
object
Pagination links for list responses.
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

signalwire-recordings-api-openapi.yml Raw ↑

Other APIs SignalWire publishes across the network.

SignalWire Calling API (JSON-RPC)
SignalWire Accounts API
SignalWire Addresses API
SignalWire AI Agents: Custom API
SignalWire AI Agents: Dialogflow API
SignalWire AI Chat API
SignalWire AI Webhooks API
SignalWire Applications API
SignalWire Available Phone Numbers API
SignalWire Call Flows API
SignalWire Calling Webhooks API
SignalWire Calls API
Where this information came from

This is an independent, third-party profile of SignalWire Recordings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.