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

Daily rooms API

The rooms API from Daily — 22 operation(s) for rooms.

Daily rooms API is one of 13 APIs that Daily publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 25 operations across 22 paths, and defines 32 schemas. It is described by OpenAPI 3.0.3, at version 1.1.1.

Requests are made against a single base URL, https://api.daily.co/v1.

25 operations 22 paths 32 schemas 1 DELETE4 GET20 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.1.1
Base URL
https://api.daily.co/v1
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

Daily rooms API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 25

Across 22 paths, the API surfaces 25 operations — 1 DELETE, 4 GET, 20 POST. Each is listed below with its method, path, parameters, and response codes.

rooms 25
GET
/rooms
/rooms
ListRooms 3 params → 200400
POST
/rooms
/rooms
CreateRoom body → 200400
GET
/rooms/{room_name}
rooms/:name
GetRoomConfig 1 param → 200400
POST
/rooms/{room_name}
rooms/:name
SetRoomConfig 1 param body → 200400
DELETE
/rooms/{room_name}
rooms/:name
DeleteRoom 1 param → 200400
GET
/rooms/{room_name}/presence
rooms/:name/presence
GetRoomPresence 4 params → 200400
POST
/rooms/{room_name}/send-app-message
rooms/:name/send-app-message
SendAppMessage 1 param body → 200400
GET
/rooms/{room_name}/get-session-data
rooms/:name/get-session-data
GetSessionData 1 param → 200400
POST
/rooms/{room_name}/set-session-data
rooms/:name/set-session-data
SetSessionData 1 param body → 200400
POST
/rooms/{room_name}/eject
rooms/:name/eject
Eject 1 param body → 200400
POST
/rooms/{room_name}/update-permissions
rooms/:name/update-permissions
UpdatePermissions 1 param body → 200400
POST
/rooms/{room_name}/recordings/start
rooms/:name/recordings/start
RoomRecordingsStart 1 param body → 200400
POST
/rooms/{room_name}/recordings/update
rooms/:name/recordings/update
RoomRecordingsUpdate 1 param body → 200400
POST
/rooms/{room_name}/recordings/stop
rooms/:name/recordings/stop
RoomRecordingsStop 1 param → 200400
POST
/rooms/{room_name}/live-streaming/start
rooms/:name/live-streaming/start
RoomLivestreamingStart 1 param body → 200400
POST
/rooms/{room_name}/live-streaming/update
rooms/:name/live-streaming/update
RoomLivestreamingUpdate 1 param body → 200400
POST
/rooms/{room_name}/live-streaming/stop
rooms/:name/live-streaming/stop
RoomLivestreamingStop 1 param → 200400
POST
/rooms/{room_name}/transcription/start
rooms/:name/transcription/start
RoomTranscriptionStart 1 param body → 200400
POST
/rooms/{room_name}/transcription/update
rooms/:name/transcription/update
RoomTranscriptionUpdate 1 param body → 200400
POST
/rooms/{room_name}/transcription/stop
rooms/:name/transcription/stop
RoomTranscriptionStop 1 param body → 200400
POST
/rooms/{room_name}/dialOut/start
rooms/:name/dialOut/start
RoomDialOutStart 1 param body → 200400
POST
/rooms/{room_name}/dialOut/sendDTMF
rooms/:name/dialOut/sendDTMF
RoomDialOutSendDTMF 1 param body → 200400
POST
/rooms/{room_name}/dialOut/stop
rooms/:name/dialOut/stop
RoomDialOutStop 1 param body → 200400
POST
/rooms/{room_name}/sipCallTransfer
rooms/:name/sipCallTransfer
RoomSipCallTransfer 1 param body → 200
POST
/rooms/{room_name}/sipRefer
rooms/:name/sipRefer
RoomSipRefer 1 param body → 200

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are room-properties (49 properties), DailyLiveStreamingOptions (14 properties), transcription-properties (12 properties), RecordingStreamingOptions (12 properties). Each schema is shown below with its type and property counts.

transcription-properties
object
12 properties
enable_terse_logging
boolean
Reduces the volume of log messages. This feature should be enabled when there are more than 200 participants in a meeting to help improve performance. See our…
dialout-properties
object
10 properties
DailyStreamingEndpoint
object
1 property 1 required
rooms-room_name_presence-get-res
object
2 properties
transcription_bucket
object
Configures an S3 bucket in which to store transcriptions. See the [S3 bucket guide](/guides/products/live-streaming-recording/storing-recordings-in-a-custom-s3…
4 properties
DailyStreamingCustomLayoutConfig
object
4 properties 2 required
DailyStreamingActiveParticipantLayoutConfig
object
1 property 1 required
DailyStreamingLayoutConfig
geo
string
Daily uses signaling servers to manage all of the participants in a given call session. In an SFU/server mode call, the server will send and receive all audio…
enforce_unique_user_ids
boolean
Configures a domain or room to disallow multiple participants from having the same userid. This feature can be enabled to prevent users from "sharing" meeting…
DailyStreamingSingleParticipantLayoutConfig
object
2 properties 2 required
recordings_template
string
Cloud recordings are stored in either Daily's S3 bucket or the customer's own S3 bucket. By default recordings are stored as {domainname}/{roomname}/{epochtime…
DailyStreamingPortraitLayoutVariant
string
rtmp_geo
string
Used to select the region where an RTMP stream should originate. In cases where RTMP streaming services aren't available in the desired region, we'll attempt t…
transcription_template
string
transcriptions can be stored in either Daily's S3 bucket or the customer's own S3 bucket. By default transcriptions are stored as {domainname}/{roomname}/{epoc…
enable_mesh_sfu
boolean
Configures a room to use multiple SFUs for a call's media. This feature enables calls to scale to large sizes and to reduce latency between participants. It is…
DailyLiveStreamingOptions
object
14 properties
DailyStreamingDefaultLayoutConfig
object
2 properties 1 required
DailyStreamingPortraitLayoutConfig
object
3 properties 1 required
RecordingStreamingOptions
object
12 properties
sfu_switchover
number
Dictates the participant count after which room topology automatically switches from Peer-to-Peer (P2P) to Selective Forwarding Unit (SFU) mode, or vice versa.…
permissions
object
Specifies the initial default permissions for a non-[meeting-owner](/guides/configurations-and-settings/controlling-who-joins-a-meetingmeeting-owner-privileges…
4 properties
auto_transcription_settings
object
Options to use when autostarttranscription is true. See [startTranscription()](/products/daily-js/instance-methods/start-transcription) for available options.
enable_multiparty_adaptive_simulcast
boolean
Configures a domain or room to use [Daily Adaptive Bitrate](/guides/building-additional-features/daily-adaptive-bitrate). When enabled, along with configuring…
disable_rtmp_geo_fallback
boolean
Disable the fall back behavior of rtmpgeo. When rtmpgeo is set, we first try to connect to a media server in desired region. If a media server is not available…
DailyStreamingOptions
object
11 properties
room-properties
object
49 properties
enable_adaptive_simulcast
boolean
Configures a domain or room to use [Daily Adaptive Bitrate](/guides/building-additional-features/daily-adaptive-bitrate). When enabled, along with configuring…
rooms-room_name-get-res
object
7 properties
recordings_bucket
object
Configures an S3 bucket in which to store recordings. See the [S3 bucket guide](/guides/products/live-streaming-recording/storing-recordings-in-a-custom-s3-buc…
5 properties
enable_transcription_storage
boolean
Live transcriptions generated can be saved as WebVTT. This flag controls if transcription started with [startTranscription()](/products/daily-js/instance-metho…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

daily-rooms-api-openapi.yml Raw ↑

Other APIs Daily publishes across the network.

Daily batch/rooms API
Daily dialin API
Daily domain API
Daily domain-dialin-config API
Daily logs API
Daily meeting-tokens API
Daily meetings API
Daily phone-numbers API
Daily presence API
Daily recordings API
Daily transcript API
Daily webhooks API
Where this information came from

This is an independent, third-party profile of Daily rooms 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.