daily-ruby 1.0.0 → 1.0.2

data/docs/PhoneNumbersApi.md

@@ -0,0 +1,304 @@
+# Daily::PhoneNumbersApi
+
+All URIs are relative to *https://api.daily.co/v1*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**buy_phone_number**](PhoneNumbersApi.md#buy_phone_number) | **POST** /buy-phone-number | /buy-phone-number |
+| [**list_available_numbers**](PhoneNumbersApi.md#list_available_numbers) | **GET** /list-available-numbers | /list-available-numbers |
+| [**purchased_phone_nunbers**](PhoneNumbersApi.md#purchased_phone_nunbers) | **GET** /purchased-phone-numbers | /purchased-phone-numbers |
+| [**release_phone_number**](PhoneNumbersApi.md#release_phone_number) | **DELETE** /release-phone-number/{id} | release-phone-number/:id |
+
+
+## buy_phone_number
+
+> Object buy_phone_number(opts)
+
+/buy-phone-number
+
+This will buy a phone number. In the POST request you can either provide the phone number you want to buy, or leave it empty. If the specified `number` is still available, it will be bought or the API will return a failure. Alternatively, if you skipped the `number` field, a random phone number from California (CA) will be bought.
+
+### Examples
+
+```ruby
+require 'time'
+require 'daily-ruby'
+# setup authorization
+Daily.configure do |config|
+  # Configure API key authorization: sec0
+  config.api_key['sec0'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['sec0'] = 'Bearer'
+end
+
+api_instance = Daily::PhoneNumbersApi.new
+opts = {
+  buy_phone_number_request: Daily::BuyPhoneNumberRequest.new # BuyPhoneNumberRequest | 
+}
+
+begin
+  # /buy-phone-number
+  result = api_instance.buy_phone_number(opts)
+  p result
+rescue Daily::ApiError => e
+  puts "Error when calling PhoneNumbersApi->buy_phone_number: #{e}"
+end
+```
+
+#### Using the buy_phone_number_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(Object, Integer, Hash)> buy_phone_number_with_http_info(opts)
+
+```ruby
+begin
+  # /buy-phone-number
+  data, status_code, headers = api_instance.buy_phone_number_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => Object
+rescue Daily::ApiError => e
+  puts "Error when calling PhoneNumbersApi->buy_phone_number_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **buy_phone_number_request** | [**BuyPhoneNumberRequest**](BuyPhoneNumberRequest.md) |  | [optional] |
+
+### Return type
+
+**Object**
+
+### Authorization
+
+[sec0](../README.md#sec0)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## list_available_numbers
+
+> list_available_numbers(opts)
+
+/list-available-numbers
+
+Search for available phone numbers to purchase
+
+### Examples
+
+```ruby
+require 'time'
+require 'daily-ruby'
+# setup authorization
+Daily.configure do |config|
+  # Configure API key authorization: sec0
+  config.api_key['sec0'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['sec0'] = 'Bearer'
+end
+
+api_instance = Daily::PhoneNumbersApi.new
+opts = {
+  areacode: 'areacode_example', # String | An areacode to search within.
+  region: 'region_example', # String | A region or state to search within. Must be an ISO 3166-2 alpha-2 code, i.e. CA for California. Cannot be used in combination with areacode.
+  city: 'city_example', # String | A specific City to search within. Example, New York. The string must be url encoded because it is a url parameter. Must be used in combination with region. Cannot be used in combination with areacode, starts_with, contains, or ends_with.
+  contains: 'contains_example', # String | A string of 3 to 7 digits that should appear somewhere in the number.
+  starts_with: 'starts_with_example', # String | A string of 3 to 7 digits that should be used as the start of a number. Cannot be used in combination with contains or ends_with.
+  ends_with: 'ends_with_example' # String | A string of 3 to 7 digits that should be used as the end of a number. Cannot be used in combination with starts_with or contains.
+}
+
+begin
+  # /list-available-numbers
+  api_instance.list_available_numbers(opts)
+rescue Daily::ApiError => e
+  puts "Error when calling PhoneNumbersApi->list_available_numbers: #{e}"
+end
+```
+
+#### Using the list_available_numbers_with_http_info variant
+
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
+
+> <Array(nil, Integer, Hash)> list_available_numbers_with_http_info(opts)
+
+```ruby
+begin
+  # /list-available-numbers
+  data, status_code, headers = api_instance.list_available_numbers_with_http_info(opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue Daily::ApiError => e
+  puts "Error when calling PhoneNumbersApi->list_available_numbers_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **areacode** | **String** | An areacode to search within. | [optional] |
+| **region** | **String** | A region or state to search within. Must be an ISO 3166-2 alpha-2 code, i.e. CA for California. Cannot be used in combination with areacode. | [optional] |
+| **city** | **String** | A specific City to search within. Example, New York. The string must be url encoded because it is a url parameter. Must be used in combination with region. Cannot be used in combination with areacode, starts_with, contains, or ends_with. | [optional] |
+| **contains** | **String** | A string of 3 to 7 digits that should appear somewhere in the number. | [optional] |
+| **starts_with** | **String** | A string of 3 to 7 digits that should be used as the start of a number. Cannot be used in combination with contains or ends_with. | [optional] |
+| **ends_with** | **String** | A string of 3 to 7 digits that should be used as the end of a number. Cannot be used in combination with starts_with or contains. | [optional] |
+
+### Return type
+
+nil (empty response body)
+
+### Authorization
+
+[sec0](../README.md#sec0)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## purchased_phone_nunbers
+
+> purchased_phone_nunbers
+
+/purchased-phone-numbers
+
+List the purchased phone numbers for this domain
+
+### Examples
+
+```ruby
+require 'time'
+require 'daily-ruby'
+# setup authorization
+Daily.configure do |config|
+  # Configure API key authorization: sec0
+  config.api_key['sec0'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['sec0'] = 'Bearer'
+end
+
+api_instance = Daily::PhoneNumbersApi.new
+
+begin
+  # /purchased-phone-numbers
+  api_instance.purchased_phone_nunbers
+rescue Daily::ApiError => e
+  puts "Error when calling PhoneNumbersApi->purchased_phone_nunbers: #{e}"
+end
+```
+
+#### Using the purchased_phone_nunbers_with_http_info variant
+
+This returns an Array which contains the response data (`nil` in this case), status code and headers.
+
+> <Array(nil, Integer, Hash)> purchased_phone_nunbers_with_http_info
+
+```ruby
+begin
+  # /purchased-phone-numbers
+  data, status_code, headers = api_instance.purchased_phone_nunbers_with_http_info
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => nil
+rescue Daily::ApiError => e
+  puts "Error when calling PhoneNumbersApi->purchased_phone_nunbers_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+This endpoint does not need any parameter.
+
+### Return type
+
+nil (empty response body)
+
+### Authorization
+
+[sec0](../README.md#sec0)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+
+
+## release_phone_number
+
+> Object release_phone_number(id)
+
+release-phone-number/:id
+
+Release a purchased number. The number is referenced by its id. A number cannot be deleted within the 14 days of purchase. Calling this API before this period expires results in an error.
+
+### Examples
+
+```ruby
+require 'time'
+require 'daily-ruby'
+# setup authorization
+Daily.configure do |config|
+  # Configure API key authorization: sec0
+  config.api_key['sec0'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  # config.api_key_prefix['sec0'] = 'Bearer'
+end
+
+api_instance = Daily::PhoneNumbersApi.new
+id = 'id_example' # String | 
+
+begin
+  # release-phone-number/:id
+  result = api_instance.release_phone_number(id)
+  p result
+rescue Daily::ApiError => e
+  puts "Error when calling PhoneNumbersApi->release_phone_number: #{e}"
+end
+```
+
+#### Using the release_phone_number_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(Object, Integer, Hash)> release_phone_number_with_http_info(id)
+
+```ruby
+begin
+  # release-phone-number/:id
+  data, status_code, headers = api_instance.release_phone_number_with_http_info(id)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => Object
+rescue Daily::ApiError => e
+  puts "Error when calling PhoneNumbersApi->release_phone_number_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **String** |  |  |
+
+### Return type
+
+**Object**
+
+### Authorization
+
+[sec0](../README.md#sec0)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+

data/docs/PinDialinInner.md

@@ -0,0 +1,22 @@
+# Daily::PinDialinInner
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **phone_number** | **String** | Associate a purchased phone number to the dialin with PIN workflow.   | [optional] |
+| **name_prefix** | **String** | An identifier or name to associate to the workflow. | [optional] |
+| **ivr_greeting** | [**PinDialinInnerIvrGreeting**](PinDialinInnerIvrGreeting.md) |  | [optional] |
+
+## Example
+
+```ruby
+require 'daily-ruby'
+
+instance = Daily::PinDialinInner.new(
+  phone_number: null,
+  name_prefix: null,
+  ivr_greeting: null
+)
+```
+

data/docs/PinDialinInnerIvrGreeting.md

@@ -0,0 +1,18 @@
+# Daily::PinDialinInnerIvrGreeting
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **message** | **String** | message to \"Say\" when user call the phone_number. | [optional] |
+
+## Example
+
+```ruby
+require 'daily-ruby'
+
+instance = Daily::PinDialinInnerIvrGreeting.new(
+  message: null
+)
+```
+

data/docs/PinlessCallUpdateRequest.md

@@ -0,0 +1,22 @@
+# Daily::PinlessCallUpdateRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **call_id** | **String** | CallId is represented by UUID and represents the sessionId in the SIP Network. | [optional] |
+| **call_domain** | **String** | Call Domain is represented by UUID and represents your Daily Domain on the SIP Network. | [optional] |
+| **sip_uri** | **String** | This SIP URI is associated to the Daily Room that you want to forward the SIP Interconnect call to. | [optional] |
+
+## Example
+
+```ruby
+require 'daily-ruby'
+
+instance = Daily::PinlessCallUpdateRequest.new(
+  call_id: null,
+  call_domain: null,
+  sip_uri: null
+)
+```
+

data/docs/PinlessDialinInner.md

@@ -0,0 +1,24 @@
+# Daily::PinlessDialinInner
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **phone_number** | **String** | Associate a purchased phone number to the Pinless dialin workflow. | [optional] |
+| **room_creation_api** | **String** | The webhook URL to trigger when an incoming call arrives. Typically, you will need to spin-up a Daily meeting room and patch the incoming call to the room. Read more in the [pinless/sip interconnect guide](/guides/products/dial-in-dial-out/dialin-pinless#incoming-call-triggers-the-webhook). | [optional] |
+| **name_prefix** | **String** | An identifier or name to associate to the workflow. | [optional] |
+| **sip_uri** | **String** | This is not a settable value, Daily returns the `sip_uri` in cases where you want to directly send the call to the SIP URI instead of the phone_number. If you dial in to the `phone_number` or this `sip_uri`, the [webhook will be triggered](/guides/products/dial-in-dial-out/dialin-pinless#incoming-call-triggers-the-webhook).     | [optional] |
+
+## Example
+
+```ruby
+require 'daily-ruby'
+
+instance = Daily::PinlessDialinInner.new(
+  phone_number: null,
+  room_creation_api: null,
+  name_prefix: null,
+  sip_uri: null
+)
+```
+

data/docs/PostWebhook.md

@@ -6,7 +6,9 @@
 | ---- | ---- | ----------- | ----- |
 | **url** | **String** | The webhook server endpoint that was provided. | [optional] |
 | **basic_auth** | **String** | The basic auth credentials that will be used to POST to the webhook URL. | [optional] |
+| **retry_type** | **String** | The retry configuration for this webhook endpoint to use. The default is circuit-breaker. | [optional] |
 | **event_types** | **Array<String>** | The set of event types this webhook is subscribed to. | [optional] |
+| **hmac** | **String** | A secret that can be used to verify the signature of the webhook. If not provided, an hmac will be provisioned for you and returned. | [optional] |
 
 ## Example
 
@@ -16,7 +18,9 @@ require 'daily-ruby'
 instance = Daily::PostWebhook.new(
   url: null,
   basic_auth: null,
-  event_types: null
+  retry_type: null,
+  event_types: null,
+  hmac: null
 )
 ```
 

data/docs/Properties.md

@@ -11,12 +11,13 @@
 | **exp** | **Integer** | \"Expires\". This is a unix timestamp (seconds since the epoch.) Users cannot join a meeting with this token after this time.  Daily strongly recommends adding an `exp` value to all meeting tokens. Learn more in our Daily blog post: [Add advanced security to video chats with the Daily API](https://www.daily.co/blog/add-advanced-security-features-to-video-chats-with-the-daily-api/) | [optional] |
 | **is_owner** | **Boolean** | The user has [meeting owner privileges](https://docs.daily.co/docs/controlling-who-joins-a-meeting#meeting-owner-privileges). For example, if the room is configured for `owner_only_broadcast` and used in a Daily Prebuilt call, this user can send video, and audio, and can screenshare. | [optional][default to false] |
 | **user_name** | **String** | The user's name in this meeting. The name displays in the user interface when the user is muted or has turned off the camera, and in the chat window. This username is also saved in the meeting events log (meeting events are retrievable using the [analytics](/reference/rest-api/meetings) API methods.) | [optional] |
-| **user_id** | **String** | The user's ID for this meeting session. This ID is retrievable using the [meetings](/reference/rest-api/meetings) API. You can use `user_id` to map between your user database and meeting events/attendance. *The ID does not display in our standard in-call UI during the call.  _max length 36 chars_ | [optional] |
+| **user_id** | **String** | The user's ID for this meeting session. During a session, this ID is retrievable in the [`participants()`](/reference/daily-js/instance-methods/participants) method and [related participant events](/reference/daily-js/events/participant-events). Either during or after a session concludes, this ID is retrievable using the [/meetings](/reference/rest-api/meetings) REST API endpoint. You can use `user_id` to map between your user database and meeting events/attendance.  For domains configured for [HIPAA compliance](/guides/privacy-and-security/hipaa), if the `user_id` value is a [UUID](https://www.ietf.org/rfc/rfc4122.txt) (for example, `f81d4fae-7dec-11d0-a765-00a0c91e6bf6`), then the UUID will be returned for the participant in the [`/meetings`](/reference/rest-api/meetings) REST API endpoint. Otherwise, the string `hipaa` will be returned in order to remove potential PHI. During a session, the provided `user_id` will always be returned through the `participants()` method and related events, regardless of the `user_id` value.  The `user_id` has a limit of 36 characters. | [optional] |
 | **enable_screenshare** | **Boolean** | Sets whether or not the user is allowed to screen share. This setting applies for the duration of the meeting. If you're looking to dynamically control whether a user can screen share during a meeting, then use the [`permissions`](/reference/rest-api/meeting-tokens/config#permissions) token property. | [optional][default to true] |
 | **start_video_off** | **Boolean** | Disable the default behavior of automatically turning on a participant's camera on a direct `join()` (i.e. without `startCamera()` first). | [optional][default to false] |
 | **start_audio_off** | **Boolean** | Disable the default behavior of automatically turning on a participant's microphone on a direct `join()` (i.e. without `startCamera()` first). | [optional][default to false] |
 | **enable_recording** | **String** | Jump to [recording docs](/reference/rest-api/recordings). | [optional] |
 | **enable_prejoin_ui** | **Boolean** | Determines whether the participant using the meeting token enters a waiting room with a camera, mic, and browser check before joining a call. If this property is also set in the room or domain's configuration, the meeting token's configuration will take priority.  ⚠️ You must be using [Daily Prebuilt](https://daily.co/prebuilt) to use `enable_prejoin_ui`. | [optional] |
+| **enable_live_captions_ui** | **Boolean** | Sets whether the participant sees a closed captions button in their Daily Prebuilt call tray. When the closed caption button is clicked, closed captions are displayed locally.  When set to `true`, a closed captions button appears in the call tray. When set to `false`, the closed captions button is hidden from the call tray.  Note: Transcription must be enabled for the room or users must have permission to start transcription for this feature to be enabled. View the [transcription guide](/guides/products/transcription) for more details.  ⚠️ You must be using [Daily Prebuilt](https://daily.co/blog/daily-prebuilt-video-chat) to use `enable_live_captions_ui`. | [optional] |
 | **enable_recording_ui** | **Boolean** | Determines whether the participant using the meeting token can see the Recording button in Daily Prebuilt's UI, which can be found in the video call tray. If this value is `false`, the button will not be included in the tray. If it's `true`, the Recording button will be displayed.  This option is useful when only specific call participants should have recording permissions.   ⚠️ You must be using [Daily Prebuilt](https://daily.co/prebuilt) to use `enable_recording_ui`. | [optional] |
 | **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 [guides for supporting large experiences](/guides/scaling-calls) for additional instruction. | [optional][default to false] |
 | **start_cloud_recording** | **Boolean** | Start cloud recording when the user joins the room. This can be used to always record and archive meetings, for example in a customer support context.  Note: This requires the `enable_recording` property of the room or token to be set to `cloud`. If you want to automatically record calls with other recording modes, use `callObject.startRecording()` after `await callObject.join()` in your code. | [optional][default to false] |
@@ -46,6 +47,7 @@ instance = Daily::Properties.new(
   start_audio_off: null,
   enable_recording: null,
   enable_prejoin_ui: null,
+  enable_live_captions_ui: null,
   enable_recording_ui: null,
   enable_terse_logging: null,
   start_cloud_recording: null,

data/docs/RecordingError.md

@@ -6,7 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **version** | **String** | The semantic version of the current message. | [optional] |
 | **type** | **String** | The type of event that is being provided. | [optional] |
-| **event_ts** | **Integer** | The Unix epoch time in seconds representing when the event was generated. | [optional] |
+| **event_ts** | **Float** | The Unix epoch time in seconds representing when the event was generated. | [optional] |
 | **payload** | [**RecordingErrorPayload**](RecordingErrorPayload.md) |  | [optional] |
 
 ## Example

data/docs/RecordingReadyToDownload.md

@@ -6,7 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **version** | **String** | The semantic version of the current message. | [optional] |
 | **type** | **String** | The type of event that is being provided. | [optional] |
-| **event_ts** | **Integer** | The Unix epoch time in seconds representing when the event was generated. | [optional] |
+| **event_ts** | **Float** | The Unix epoch time in seconds representing when the event was generated. | [optional] |
 | **payload** | [**RecordingReadyToDownloadPayload**](RecordingReadyToDownloadPayload.md) |  | [optional] |
 
 ## Example

data/docs/RecordingStarted.md

@@ -6,7 +6,7 @@
 | ---- | ---- | ----------- | ----- |
 | **version** | **String** | The semantic version of the current message. | [optional] |
 | **type** | **String** | The type of event that is being provided. | [optional] |
-| **event_ts** | **Integer** | The Unix epoch time in seconds representing when the event was generated. | [optional] |
+| **event_ts** | **Float** | The Unix epoch time in seconds representing when the event was generated. | [optional] |
 | **payload** | [**RecordingStartedPayload**](RecordingStartedPayload.md) |  | [optional] |
 
 ## Example

data/docs/RoomDialOutSendDTMFRequest.md

@@ -0,0 +1,20 @@
+# Daily::RoomDialOutSendDTMFRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **session_id** | **String** |  | [optional] |
+| **tones** | **String** |  | [optional] |
+
+## Example
+
+```ruby
+require 'daily-ruby'
+
+instance = Daily::RoomDialOutSendDTMFRequest.new(
+  session_id: null,
+  tones: null
+)
+```
+

data/docs/RoomDialOutStopRequest.md

@@ -0,0 +1,18 @@
+# Daily::RoomDialOutStopRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **session_id** | **String** |  | [optional] |
+
+## Example
+
+```ruby
+require 'daily-ruby'
+
+instance = Daily::RoomDialOutStopRequest.new(
+  session_id: null
+)
+```
+

data/docs/RoomProperties.md

@@ -12,6 +12,7 @@
 | **enable_emoji_reactions** | **Boolean** | Determines if [Daily Prebuilt](https://www.daily.co/prebuilt) displays the Emoji Reactions UI. When set to `true`, a Reactions button appears in the call tray. This button allows users to select and send a reaction into the call. When set to `false`, the Reactions button is hidden and the feature is disabled.  Usage: This feature is a good fit for meetings when a host or presenter would benefit from receiving nonverbal cues from the audience. It's also great to keep meetings fun.  ⚠️ This flag only applies to Daily Prebuilt. It has no effect when building custom video applications with the Daily call object. | [optional] |
 | **enable_hand_raising** | **Boolean** | Sets whether the participants in the room can use [Daily Prebuilt](https://www.daily.co/prebuilt)'s hand raising controls. When set to `true`, an additional button will be available in Daily Prebuilt's UI to toggle a hand raise.  ⚠️ This flag only applies to Daily Prebuilt. It has no effect when building custom video applications with the Daily call object. | [optional] |
 | **enable_prejoin_ui** | **Boolean** | Determines whether participants enter a waiting room with a camera, mic, and browser check before joining a call.  ⚠️ You must be using [Daily Prebuilt](https://daily.co/prebuilt) to use `enable_prejoin_ui`. | [optional] |
+| **enable_live_captions_ui** | **Boolean** | Sets whether participants in a room see a closed captions button in their Daily Prebuilt call tray. When the closed caption button is clicked, closed captions are displayed locally.  When set to `true`, a closed captions button appears in the call tray. When set to `false`, the closed captions button is hidden from the call tray.  Note: Transcription must be enabled for the room or users must have permission to start transcription for this feature to be enabled. View the [transcription guide](/guides/products/transcription) for more details.  ⚠️ You must be using [Daily Prebuilt](https://daily.co/blog/daily-prebuilt-video-chat) to use `enable_live_captions_ui`. | [optional] |
 | **enable_network_ui** | **Boolean** | Determines whether the network button, and the network panel it reveals on click, appears in this room.  ⚠️ You must be using [Daily Prebuilt](https://daily.co/prebuilt) to use `enable_network_ui`. | [optional] |
 | **enable_noise_cancellation_ui** | **Boolean** | Determines whether Daily Prebuilt displays noise cancellation controls. When set to `true`, a participant can enable microphone noise cancellation during a Daily Prebuilt call. ⚠️ This flag only applies to [Daily Prebuilt](https://daily.co/prebuilt). It has no effect when building custom video applications with the Daily call object. To learn more about adding noise cancellation to a custom application, see the [`updateInputSettings()` docs](/reference/daily-js/instance-methods/update-input-settings). | [optional] |
 | **enable_breakout_rooms** | **Boolean** | Sets whether [Daily Prebuilt](https://www.daily.co/prebuilt)’s breakout rooms feature is enabled. When set to `true`, an owner in a Prebuilt call can create breakout rooms to divide participants into smaller, private groups.   ⚠️ You must be using [Daily Prebuilt](https://daily.co/blog/daily-prebuilt-video-chat) to use `enable_breakout_rooms`.  ⚠️ This property is in beta. | [optional] |
@@ -19,6 +20,7 @@
 | **enable_screenshare** | **Boolean** | Sets whether users in a room can screen share during a session. This property cannot be changed after a session starts. For dynamic control over permissions, use the [`updateParticipant()`](/reference/daily-js/instance-methods/update-participant#permissions) method to control user permissions. | [optional][default to true] |
 | **enable_video_processing_ui** | **Boolean** | Determines whether Daily Prebuilt displays background blur controls. When set to `true`, a participant can enable blur during a Daily Prebuilt call.  ⚠️ This flag only applies to Daily Prebuilt. It has no effect when building custom video applications with the Daily call object. | [optional][default to true] |
 | **enable_chat** | **Boolean** | This property is one of [multiple ways to add chat to Daily video calls](https://www.daily.co/blog/three-ways-to-add-chat-to-your-video-calls-with-the-daily-api/). | [optional][default to false] |
+| **enable_shared_chat_history** | **Boolean** | When enabled, newly joined participants in Prebuilt calls will request chat history from remote peers, in order to view chat messages from before they joined. | [optional][default to true] |
 | **start_video_off** | **Boolean** | Disable the default behavior of automatically turning on a participant's camera on a direct `join()` (i.e. without `startCamera()` first). | [optional][default to false] |
 | **start_audio_off** | **Boolean** | Disable the default behavior of automatically turning on a participant's microphone on a direct `join()` (i.e. without `startCamera()` first). | [optional][default to false] |
 | **owner_only_broadcast** | **Boolean** | In Daily Prebuilt, only the meeting owners will be able to turn on camera, unmute mic, and share screen.  See [setting up calls](https://docs.daily.co/docs/setting-up-calls). | [optional][default to false] |
@@ -28,10 +30,13 @@
 | **enable_advanced_chat** | **Boolean** | Property that gives end users a richer chat experience. This includes:  * Emoji reactions to chat messages * Emoji picker in the chat input form * Ability to send a Giphy chat message  ⚠️ This flag only applies to Daily Prebuilt. It has no effect when building custom video applications with the Daily call object. | [optional][default to false] |
 | **enable_hidden_participants** | **Boolean** | When enabled, non-owner users join a meeting with a hidden presence, meaning they won't appear as a named participant in the meeting and have no [participant events](https://docs.daily.co/reference/daily-js/events/participant-events) associated to them. Additionally, these participants can _only_ receive media tracks from owner participants.  Hidden participants can be tracked using the [`participantCounts()`](/reference/daily-js/instance-methods/participant-counts) method. Hidden participants do _not_ have entries in the [`participants()`](/reference/daily-js/instance-methods/participants) method return value.  When used with [Daily Prebuilt](/guides/products/prebuilt), hidden participants are included in the participant count available in the UI; however, are _not_ included in the People panel and can only read chat messages.  This property should be used to support hosting large meetings. See our [guide on interactive live streaming](/guides/scaling-calls/interactive-live-streaming-rtmp-output#interactive-live-streaming-up-to-100-000-participants) for additional instruction. | [optional][default to false] |
 | **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 recommended specifically for interactive live streaming.  See our [guide for interactive live streaming](/guides/scaling-calls/interactive-live-streaming-rtmp-output#daily-prebuilt-configurations-to-support-100-000-participants) for additional instruction. | [optional] |
-| **sfu_switchover** | **Float** | Dictates the participant count after which room topology automatically switches from Peer-to-Peer (P2P) to Selective Forwarding Unit (SFU) mode, or vice versa.  For example, if `sfu_switchover` is set to `3` and the current network topology is P2P, the topology will switch to SFU mode when the _fourth_ participant joins the call. If the current topology is SFU, it will switch to P2P mode when the participant count decreases from `3` to `2`.  We recommend specifying an integer value for this property except for cases where you would like the room to switch to SFU mode as soon as the first participant joins. In this case, set `sfu_switchover` to `0.5`.  See our [guide about video call architecture](/guides/architecture-and-monitoring/intro-to-video-arch#the-architecture-of-a-room-p2p-vs-sfu-calls) for additional information. | [optional][default to 2] |
+| **sfu_switchover** | **Float** | Dictates the participant count after which room topology automatically switches from Peer-to-Peer (P2P) to Selective Forwarding Unit (SFU) mode, or vice versa.  For example, if `sfu_switchover` is set to `2` and the current network topology is P2P, the topology will switch to SFU mode when the _third_ participant joins the call. If the current topology is SFU, it will switch to P2P mode when the participant count decreases from `2` to `1`.  We recommend specifying an integer value for this property except for cases where you would like the room to switch to SFU mode as soon as the first participant joins. In this case, set `sfu_switchover` to `0.5`.  See our [guide about video call architecture](/guides/architecture-and-monitoring/intro-to-video-arch#the-architecture-of-a-room-p2p-vs-sfu-calls) for additional information. | [optional][default to 0.5] |
+| **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 the client to [`allowAdaptiveLayers`](/reference/daily-js/instance-methods/update-send-settings#sendsettings), the Daily client will continually adapt send settings to the current network conditions. `allowAdaptiveLayers` is `true` by default; if you haven't modified that setting, then setting `enable_adaptive_simulcast` to `true` will enable Daily Adaptive Bitrate for 1:1 calls. | [optional][default to true] |
+| **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 the client to [`allowAdaptiveLayers`](/reference/daily-js/instance-methods/update-send-settings#sendsettings), the Daily client will continually adapt send settings to the current network conditions. `allowAdaptiveLayers` is `true` by default; if you haven't modified that setting, then setting `enable_multiparty_adaptive_simulcast` to `true` will enable Daily Adaptive Bitrate for multi-party calls. To use this feature, `enable_adaptive_simulcast` must also be set to `true`. | [optional][default to false] |
+| **enforce_unique_user_ids** | **Boolean** | Configures a domain or room to disallow multiple participants from having the same `user_id`. This feature can be enabled to prevent users from \"sharing\" meeting tokens. When enabled, a participant joining or reconnecting to a meeting will cause existing participants with the same user_id to be ejected. | [optional][default to false] |
 | **experimental_optimize_large_calls** | **Boolean** | Enables Daily Prebuilt to support group calls of up to 1,000 participants and [owner only broadcast](/reference/rest-api/rooms/config#owner_only_broadcast) calls of up to 100K participants.  When set to true, Daily Prebuilt will: - Automatically mute the local user on joining - Update grid view to show a maximum of 12 users in the grid at a time - Allow only 16 users to be unmuted at the same time. When more than 16 users are unmuted, the oldest active speaker will be automatically muted.  See our [guide on large real-time calls](/guides/scaling-calls/large-real-time-calls) for additional instruction.  ⚠️ This flag only applies to Daily Prebuilt. It has no effect when building custom video applications with the Daily call object. | [optional] |
 | **lang** | **String** | The default language of the [Daily prebuilt video call UI](/guides/products/prebuilt#daily-prebuilt-ui), for this room.  Setting the language at the room level will override any domain-level language settings you have.  Read more about [changing prebuilt UI language settings](https://help.daily.co/en/articles/4579930-changing-the-language-setting-of-the-prebuilt-ui).  `*` Norwegian `\"no\"` and Russian `\"ru\"` are only available in the new Daily Prebuilt. | [optional][default to 'en'] |
-| **meeting_join_hook** | **String** | Sets a URL that will receive a webhook when a user joins a room. Default is NULL. Character limit for webhook URL is 255.  More resources: - [Configuring a webhook to send notifications when someone joins your video calls](https://www.daily.co/blog/configure-a-webhook-to-send-notifications-when-someone-joins-your-video-calls/) | [optional] |
+| **meeting_join_hook** | **String** | Sets a URL that will receive a webhook when a user joins a room. Default is NULL. Character limit for webhook URL is 255.  ⚠️ In place of the `meeting_join_hook`, we recommend setting up a [webhook](/reference/rest-api/webhooks) and listening for the [`participant.joined`](/reference/rest-api/webhooks/events/participant-joined) event. | [optional] |
 | **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 and video from each participant. In a peer-to-peer call, each participant sends media directly to and from each other peer, but a signaling server still manages call state.  Daily runs servers in several different AWS regions to minimize latency for users around the world. The job of 'picking' a call server is handled when the first participant joins a room. The first participant's browser connects to a call server using Amazon's Route 53 DNS resolution, which chooses a server in the region closest to them.  This isn't always optimal. For example, if one person joins in London, and then ten more people join from Cape Town, the call will still be hosted out of `eu-west-2` . The majority of the participants will have higher latency to the server than if one of them had joined first and the call was being hosted in `af-south-1`. In cases like this, you may want to configure your domain (or a specific room) to always choose a call server in a specific AWS region.  Available regions: - `\"af-south-1\"` (Cape Town) - `\"ap-northeast-2\"` (Seoul) - `\"ap-southeast-1\"` (Singapore) - `\"ap-southeast-2\"` (Sydney) - `\"ap-south-1\"` (Mumbai) - `\"eu-central-1\"` (Frankfurt) - `\"eu-west-2\"` (London) - `\"sa-east-1\"` (São Paulo) - `\"us-east-1\"` (N. Virginia) - `\"us-west-2\"` (Oregon) | [optional][default to 'NULL'] |
 | **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 to fall back to the default region based on the SFU being used for the meeting.    Available regions:   - `\"us-west-2\"` (Oregon)   - `\"eu-central-1\"` (Frankfurt)   - `\"ap-south-1\"` (Mumbai)    The default regions are grouped based on the SFU region like so:   - RTMP region `\"us-west-2\"` includes SFU regions: `\"us-west-2\"`, `\"us-east-1\"`, `\"sa-east-1\"`   - RTMP region `\"eu-central-1\"` includes SFU regions: `\"eu-central-1\"`, `\"eu-west-2\"`, `\"af-south-1\"`   - RTMP region `\"ap-south-1\"` includes SFU regions: `\"ap-southeast-1\"`, `\"ap-southeast-2\"`, `\"ap-northeast-2\"`, `\"ap-south-1\"` | [optional][default to 'The closest available region to the SFU region used by the meeting.'] |
 | **disable_rtmp_geo_fallback** | **Boolean** | Disable the fall back behavior of rtmp_geo. When rtmp_geo is set, we first try to connect to a media server in desired region. If a media server is not available in the desired region, we fall back to default region based on SFU's region. This property disables this automatic fall back. When this property is set, we will trigger a recording/streaming error event when media worker is unavailable. Also, the client should retry recording/streaming. | [optional][default to false] |
@@ -58,6 +63,7 @@ instance = Daily::RoomProperties.new(
   enable_emoji_reactions: null,
   enable_hand_raising: null,
   enable_prejoin_ui: null,
+  enable_live_captions_ui: null,
   enable_network_ui: null,
   enable_noise_cancellation_ui: null,
   enable_breakout_rooms: null,
@@ -65,6 +71,7 @@ instance = Daily::RoomProperties.new(
   enable_screenshare: null,
   enable_video_processing_ui: null,
   enable_chat: null,
+  enable_shared_chat_history: null,
   start_video_off: null,
   start_audio_off: null,
   owner_only_broadcast: null,
@@ -75,6 +82,9 @@ instance = Daily::RoomProperties.new(
   enable_hidden_participants: null,
   enable_mesh_sfu: null,
   sfu_switchover: null,
+  enable_adaptive_simulcast: null,
+  enable_multiparty_adaptive_simulcast: null,
+  enforce_unique_user_ids: null,
   experimental_optimize_large_calls: null,
   lang: null,
   meeting_join_hook: null,

data/docs/RoomSipCallTransferRequest.md

@@ -0,0 +1,20 @@
+# Daily::RoomSipCallTransferRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **session_id** | **String** |  | [optional] |
+| **to_end_point** | **String** |  | [optional] |
+
+## Example
+
+```ruby
+require 'daily-ruby'
+
+instance = Daily::RoomSipCallTransferRequest.new(
+  session_id: null,
+  to_end_point: null
+)
+```
+