Skip to content
OpenParablePublic APIs

Twilio - Video API

by twilio.com

HTTP BasicHTTPSPhone
Open documentation ↗

Overview

This is the public Twilio REST API.

Twilio - Video is a phone API from twilio.com. Requests are authenticated with HTTP Basic auth. It is served over HTTPS. Its OpenAPI description documents 35 endpoints.

At a glance

Authentication
HTTP Basic
HTTPS
Yes
CORS
Unknown
Category
Phone
Base URL
https://video.twilio.com
Version
1.42.0
Endpoints
35
OpenAPI
Specification ↗
Spec updated
2023-04-20

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL
curl -X GET "https://video.twilio.com/v1/CompositionHooks" \
  -H "Accept: application/json" \
  -H "Authorization: Basic BASE64_USER_PASSWORD"
JavaScript
const response = await fetch("https://video.twilio.com/v1/CompositionHooks", {
  method: "GET",
  headers: {
    "Accept": "application/json",
    "Authorization": "Basic BASE64_USER_PASSWORD",
  },
});
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    "GET",
    "https://video.twilio.com/v1/CompositionHooks",
    headers={
    "Accept": "application/json",
    "Authorization": "Basic BASE64_USER_PASSWORD",
    },
    timeout=30,
)
print(response.json())

Endpoints

MethodPathWhat it does
GET/v1/CompositionHooksList of all Recording CompositionHook resources.
POST/v1/CompositionHooksCreateCompositionHook
GET/v1/CompositionHooks/{Sid}Returns a single CompositionHook resource identified by a CompositionHook SID.
POST/v1/CompositionHooks/{Sid}UpdateCompositionHook
DELETE/v1/CompositionHooks/{Sid}Delete a Recording CompositionHook resource identified by a `CompositionHook SID`.
GET/v1/CompositionSettings/DefaultFetchCompositionSettings
POST/v1/CompositionSettings/DefaultCreateCompositionSettings
GET/v1/CompositionsList of all Recording compositions.
POST/v1/CompositionsCreateComposition
GET/v1/Compositions/{Sid}Returns a single Composition resource identified by a Composition SID.
DELETE/v1/Compositions/{Sid}Delete a Recording Composition resource identified by a Composition SID.
GET/v1/RecordingSettings/DefaultFetchRecordingSettings
POST/v1/RecordingSettings/DefaultCreateRecordingSettings
GET/v1/RecordingsList of all Track recordings.
GET/v1/Recordings/{Sid}Returns a single Recording resource identified by a Recording SID.
DELETE/v1/Recordings/{Sid}Delete a Recording resource identified by a Recording SID.
GET/v1/RoomsListRoom
POST/v1/RoomsCreateRoom
GET/v1/Rooms/{RoomSid}/ParticipantsListRoomParticipant
GET/v1/Rooms/{RoomSid}/Participants/{ParticipantSid}/PublishedTracksReturns a list of tracks associated with a given Participant. Only `currently` Published Tracks are in the list resource.
GET/v1/Rooms/{RoomSid}/Participants/{ParticipantSid}/PublishedTracks/{Sid}Returns a single Track resource represented by TrackName or SID.
GET/v1/Rooms/{RoomSid}/Participants/{ParticipantSid}/SubscribeRulesReturns a list of Subscribe Rules for the Participant.
POST/v1/Rooms/{RoomSid}/Participants/{ParticipantSid}/SubscribeRulesUpdate the Subscribe Rules for the Participant
GET/v1/Rooms/{RoomSid}/Participants/{ParticipantSid}/SubscribedTracksReturns a list of tracks that are subscribed for the participant.
GET/v1/Rooms/{RoomSid}/Participants/{ParticipantSid}/SubscribedTracks/{Sid}Returns a single Track resource represented by `track_sid`. Note: This is one resource with the Video API that requires a SID, be Track Name on the subscriber
GET/v1/Rooms/{RoomSid}/Participants/{Sid}FetchRoomParticipant
POST/v1/Rooms/{RoomSid}/Participants/{Sid}UpdateRoomParticipant
POST/v1/Rooms/{RoomSid}/Participants/{Sid}/AnonymizeUpdateRoomParticipantAnonymize
GET/v1/Rooms/{RoomSid}/RecordingRulesReturns a list of Recording Rules for the Room.
POST/v1/Rooms/{RoomSid}/RecordingRulesUpdate the Recording Rules for the Room
GET/v1/Rooms/{RoomSid}/RecordingsListRoomRecording
GET/v1/Rooms/{RoomSid}/Recordings/{Sid}FetchRoomRecording
DELETE/v1/Rooms/{RoomSid}/Recordings/{Sid}DeleteRoomRecording
GET/v1/Rooms/{Sid}FetchRoom
POST/v1/Rooms/{Sid}UpdateRoom

Questions

Does the Twilio - Video API need an API key?

Yes. The Twilio - Video API uses HTTP Basic authentication; the documentation explains how to get credentials.

Does the Twilio - Video API support HTTPS?

Yes, the Twilio - Video API is served over HTTPS.

How many endpoints does the Twilio - Video API have?

Its OpenAPI description lists 35 endpoints in version 1.42.0. All of them are shown on this page.

What are alternatives to the Twilio - Video API?

Other Phone APIs include Twilio - Accounts, ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management, Twilio - Api, Mobility API, Telnyx API.

Compare alternatives →

Twilio - Accounts

Phone

This is the public Twilio REST API.

HTTP Basic13 endpoints

ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management

Phone

ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management described using OpenAPI.

No auth16 endpoints

Twilio - Api

Phone

This is the public Twilio REST API.

HTTP Basic199 endpoints

Mobility API

Phone

Transit API can be used to obtain time-aggregated data representing moving the people between various spatial points within the Czech Republic. Having A - 'from' and B - 'to' points, the API can return count of people traveling from A to B or people that are from A and traveling to B, etc. The mobility data is based on moving mobile stations in O2 mobile network.

No auth2 endpoints

Telnyx API

Phone

SIP trunking, SMS, MMS, Call Control and Telephony Data Services.

Bearer token361 endpoints

Twilio - Autopilot

Phone

This is the public Twilio REST API.

HTTP Basic52 endpoints

Listed from APIs.guru (CC0).