zoom_us 0.1.1

data/spec/api/chat_messages_api_spec.rb

@@ -0,0 +1,91 @@
+=begin
+#Zoom API
+
+#The Zoom API allows developers to safely and securely access information from Zoom. You can use this API to build private services or public applications on the [Zoom App Marketplace](http://marketplace.zoom.us). To learn how to get your credentials and create private/public applications, read our [Authorization Guide](https://marketplace.zoom.us/docs/guides/authorization/credentials). All endpoints are available via `https` and are located at `api.zoom.us/v2/`.  For instance you can list all users on an account via `https://api.zoom.us/v2/users/`.
+
+OpenAPI spec version: 2.0.0
+Contact: developersupport@zoom.us
+Generated by: https://github.com/swagger-api/swagger-codegen.git
+Swagger Codegen version: 2.4.12
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ZoomUs::ChatMessagesApi
+# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
+# Please update as you see appropriate
+describe 'ChatMessagesApi' do
+  before do
+    # run before each test
+    @instance = ZoomUs::ChatMessagesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ChatMessagesApi' do
+    it 'should create an instance of ChatMessagesApi' do
+      expect(@instance).to be_instance_of(ZoomUs::ChatMessagesApi)
+    end
+  end
+
+  # unit tests for delete_chat_message
+  # Delete a Message
+  # Delete a chat message that you previously sent to a contact or a channel. In the query parameter, you must provide either of the following:<br> * `to_contact`: The email address of the contact to whom you sent the message. Use this parameter to delete a message sent to an individual contact in Zoom. * `to_channel`: The channel ID of the channel where you sent the message. Use this parameter to delete a message sent to a channel in Zoom.  <p style=\"background-color:#e1f5fe;color:#01579b;padding:8px\"> <b>Note: </b>This API only supports <b>user-managed</b> <a href=\"https://marketplace.zoom.us/docs/guides/getting-started/app-types/create-oauth-app\">OAuth app</a>.</p><br>  **Scope:** `chat_message:write`<br>   
+  # @param message_id Message ID
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :to_contact The userId or email address of a chat contact to whom you previously sent the message.  Note: You must provide either `to_contact` or `to_channel` as a query parameter to delete a message that was previously sent to either an individual or a chat channel respectively. 
+  # @option opts [String] :to_channel The channel Id of the channel where you would like to send the message.  You must provide either `to_contact` or `to_channel` as a query parameter to delete a message that was previously sent to either an individual or a chat channel 
+  # @return [Object]
+  describe 'delete_chat_message test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for edit_message
+  # Update a Message
+  # Each chat message has a unique identifier. Use this API to edit a chat message that you previously sent to either a contact or a channel in Zoom by providing the ID of the message as the value of the `messageId` parameter. The ID can be retrieved from List User's Chat Messages API. Additionally, as a query parameter, you must provide either the **email address** of the contact or the **Channel ID** of the channel where the message was sent.   <p style=\"background-color:#e1f5fe; color:#01579b; padding:8px\"> <b>Note: </b> This API only supports <b>user-managed</b> <a href=\"https://marketplace.zoom.us/docs/guides/getting-started/app-types/create-oauth-app\">OAuth app</a>.</p><br>  **Scope:** `chat_message:write` <br>      
+  # @param message_id Message ID: Unique Identifier of the message.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Body6] :body 
+  # @return [nil]
+  describe 'edit_message test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_chat_messages
+  # List User's Chat Messages
+  # A Zoom user can have conversations with other Zoom users via chat. Use this API to list the current user's chat messages between the user and an individual contact or a chat channel.<br> In the query parameter, you must provide either of the following:<br> * `to_contact`: The email address of the contact with whom the user conversed by sending/receiving messages. * `to_channel`: The channel ID of the channel to/from which the user has sent and/or received messages. <br> **Specify a date** in the `date` query parameter to view messages from that date. If a date is not provided, the default value for the query will be the **current date**.<br> <p style=\"background-color:#e1f5fe; color:#01579b; padding:8px\"><b>Note: </b>This API only supports <b>user-managed</b> <a href=\"https://marketplace.zoom.us/docs/guides/getting-started/app-types/create-oauth-app\">OAuth app</a>.</p><br>  <br>**Scopes:** `chat_message:read`<br>    
+  # @param user_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :to_contact The email address of a chat contact with whom the current user chatted. Messages that were sent and/or received between the user and the contact is displayed.  Note: You must provide either `contact` or `channel` as a query parameter to retrieve messages either from an individual or a chat channel. 
+  # @option opts [String] :to_channel The channel Id of a channel inside which current user had chat converstations. Messages that were sent and/or received between the user and the channel is displayed.  Note: You must provide either `contact` or `channel` as a query parameter to retrieve messages either from an individual or a chat channel. 
+  # @option opts [Date] :date_ The query date for which you would like to get the chat messages.
+  # @option opts [Integer] :page_size The number of records returned with a single API call. 
+  # @option opts [String] :next_page_token The next page token is used to paginate through large result sets. A next page token will be returned whenever the set of available results exceeds the current page size. The expiration period for this token is 15 minutes.
+  # @return [InlineResponse2006]
+  describe 'get_chat_messages test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for senda_chat_message
+  # Send a Chat Message
+  # Send chat messages on Zoom to either an individual user who is in your contact list or to a [channel](https://support.zoom.us/hc/en-us/articles/200912909-Getting-Started-With-Channels-Group-Messaging-) of which you are a member. To send a message to a contact, provide the contact's email address in the `to_contact` field. Similary, to send a message to a channel, provide the Channel Id of the Channel in `to_channel` field.<br>  <br>**Scopes:** `chat_message:write`<br>   <br>  <p style=\"background-color:#e1f5fe; color:#01579b; padding:8px\"> <b>Note: </b>This API only supports <b>user-managed</b>  <a href=\"https://marketplace.zoom.us/docs/guides/getting-started/app-types/create-oauth-app\">OAuth app</a>.</p><br> 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Body5] :body 
+  # @return [InlineResponse2011]
+  describe 'senda_chat_message test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/chatbot_messages_api_spec.rb

@@ -0,0 +1,73 @@
+=begin
+#Zoom API
+
+#The Zoom API allows developers to safely and securely access information from Zoom. You can use this API to build private services or public applications on the [Zoom App Marketplace](http://marketplace.zoom.us). To learn how to get your credentials and create private/public applications, read our [Authorization Guide](https://marketplace.zoom.us/docs/guides/authorization/credentials). All endpoints are available via `https` and are located at `api.zoom.us/v2/`.  For instance you can list all users on an account via `https://api.zoom.us/v2/users/`.
+
+OpenAPI spec version: 2.0.0
+Contact: developersupport@zoom.us
+Generated by: https://github.com/swagger-api/swagger-codegen.git
+Swagger Codegen version: 2.4.12
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ZoomUs::ChatbotMessagesApi
+# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
+# Please update as you see appropriate
+describe 'ChatbotMessagesApi' do
+  before do
+    # run before each test
+    @instance = ZoomUs::ChatbotMessagesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ChatbotMessagesApi' do
+    it 'should create an instance of ChatbotMessagesApi' do
+      expect(@instance).to be_instance_of(ZoomUs::ChatbotMessagesApi)
+    end
+  end
+
+  # unit tests for delete_a_chatbot_message
+  # Delete a Chatbot Message
+  # Delete a message that was sent by your chatbot app.   **Scopes:** `imchat:bot`<br>  **Authorization Flow**: Client Credentials Flow<br><br> To get authorized, make a POST request to `/oauth/token` endpoint with grant type as `client_credentials`. <br>Use `https://api.zoom.us/oauth/token?grant_type=client_credentials` as the endpoint for the request.  You will need to send your ClientID and Secret as a Basic base64 encoded AUthorization header. Ex. `Basic base64Encode({client_id}:{client_sceret})`<br><br> Next, use the token received (access_token) as a bearer token while making the DELETE /im/chat/messages/{message_id} request to delete a message.<br><br> Learn more about how to authotize chatbots in the [Chatbot Authorization](https://marketplace.zoom.us/docs/guides/chatbots/authorization) guide.
+  # @param message_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Body41] :body 
+  # @return [InlineResponse20058]
+  describe 'delete_a_chatbot_message test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for edit_chatbot_message
+  # Edit a Chatbot Message
+  # Edit a message that was [sent](https://marketplace.zoom.us/docs/api-reference/zoom-api/im-chat/sendchatbot) by your Chatbot app.<br> After sending a message using the Send Chatbot Message API, you must store the messageId returned in the response so that you can make edits to the associated message using this API.  **Scope:** `imchat:bot`<br><br> **Authorization Flow**: Client Credentials Flow<br><br> To get authorized, make a POST request to `/oauth/token` endpoint with grant type as `client_credentials`. <br>Use `https://api.zoom.us/oauth/token?grant_type=client_credentials` as the endpoint for the request.  You will need to send your ClientID and Secret as a Basic base64 encoded AUthorization header. Ex. `Basic base64Encode({client_id}:{client_sceret})`<br><br> Next, use the token received (access_token) as a bearer token while making the PUT /im/chat/messages/{message_id} request to edit a chatbot message.<br><br> Learn more about how to authotize chatbots in the [Chatbot Authorization](https://marketplace.zoom.us/docs/guides/chatbots/authorization) guide.
+  # @param message_id Unique Identifier of the message that needs to be updated. This should be retrieved from the response of [Send Chatbot Message API](https://marketplace.zoom.us/docs/api-reference/zoom-api/im-chat/sendchatbot).
+  # @param [Hash] opts the optional parameters
+  # @option opts [Body40] :body 
+  # @return [InlineResponse20057]
+  describe 'edit_chatbot_message test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for sendchatbot
+  # Send Chatbot Messages
+  # Send chatbot messages from your marketplace chatbot app.<br><br> **Scopes:** `imchat:bot`<br> **Authorization Flow**: Client Credentials Flow<br><br> To get authorized, make a POST request to `/oauth/token` endpoint with grant type as `client_credentials`. <br>Use `https://api.zoom.us/oauth/token?grant_type=client_credentials` as the endpoint for the request.  You will need to send your ClientID and Secret as a Basic base64 encoded AUthorization header. Ex. `Basic base64Encode({client_id}:{client_sceret})`<br><br> Next, use the token recieved (access_token) as a bearer token while making the POST /im/chat/messages request to send chatbot messages.<br><br> Learn more about how to authorize chatbots in the [Chatbot Authorization](https://marketplace.zoom.us/docs/guides/chatbots/authorization) guide.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Body39] :body 
+  # @return [nil]
+  describe 'sendchatbot test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/cloud_recording_api_spec.rb

@@ -0,0 +1,227 @@
+=begin
+#Zoom API
+
+#The Zoom API allows developers to safely and securely access information from Zoom. You can use this API to build private services or public applications on the [Zoom App Marketplace](http://marketplace.zoom.us). To learn how to get your credentials and create private/public applications, read our [Authorization Guide](https://marketplace.zoom.us/docs/guides/authorization/credentials). All endpoints are available via `https` and are located at `api.zoom.us/v2/`.  For instance you can list all users on an account via `https://api.zoom.us/v2/users/`.
+
+OpenAPI spec version: 2.0.0
+Contact: developersupport@zoom.us
+Generated by: https://github.com/swagger-api/swagger-codegen.git
+Swagger Codegen version: 2.4.12
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ZoomUs::CloudRecordingApi
+# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
+# Please update as you see appropriate
+describe 'CloudRecordingApi' do
+  before do
+    # run before each test
+    @instance = ZoomUs::CloudRecordingApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of CloudRecordingApi' do
+    it 'should create an instance of CloudRecordingApi' do
+      expect(@instance).to be_instance_of(ZoomUs::CloudRecordingApi)
+    end
+  end
+
+  # unit tests for get_account_cloud_recording
+  # List Recordings of an Account
+  # List [Cloud Recordings](https://support.zoom.us/hc/en-us/articles/203741855-Cloud-Recording) available on an Account.  **Prerequisites**:<br> * A Pro or a higher paid plan with Cloud Recording option enabled.<br> **Scopes**: `recording:read:admin` or `account:read:admin`  If the scope `recording:read:admin` is used, the Account ID of the Account must be provided in the `accountId` path parameter to list recordings that belong to the Account. This scope only works for Sub Accounts.   To list recordings of a Master Account, the scope must be `account:read:admin` and the value of `accountId` should be `me`.<br> <br> 
+  # @param account_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :page_size The number of records returned within a single API call.
+  # @option opts [String] :next_page_token The next page token is used to paginate through large result sets. A next page token will be returned whenever the set of available results exceeds the current page size. The expiration period for this token is 15 minutes.
+  # @option opts [DateTime] :from The start date for the monthly range for which you would like to retrieve recordings. The maximum range can be a month. The month should fall within the past six months period from the date of query.
+  # @option opts [DateTime] :to The end date for the monthly range for which you would like to retrieve recordings. The maximum range can be a month. The month should fall within the past six months period from the date of query.
+  # @return [InlineResponse20073]
+  describe 'get_account_cloud_recording test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for meeting_recording_registrant_create
+  # Create a Recording Registrant
+  # Cloud Recordings of past Zoom Meetings can be made [on-demand](https://support.zoom.us/hc/en-us/articles/360000488283-On-demand-Recordings). Users should be [registered](https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/meetingrecordingregistrantcreate) to view these recordings.  Use this API to register a user to gain access to **On-demand Cloud Recordings** of a past meeting.<br> **Scopes:** `recording:write:admin`, `recording:write`.<br>    
+  # @param meeting_id The meeting ID.
+  # @param body 
+  # @param [Hash] opts the optional parameters
+  # @return [InlineResponse20113]
+  describe 'meeting_recording_registrant_create test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for meeting_recording_registrant_status
+  # Update Recording Registrant's Status
+  # A registrant can either be approved or denied from viewing the [on-demand](https://support.zoom.us/hc/en-us/articles/360000488283-On-demand-Recordings) recording.  Use this API to update a registrant's status.  **Scopes:** `recording:write:admin`, `recording:write`<br>   
+  # @param meeting_id The meeting ID.
+  # @param body 
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'meeting_recording_registrant_status test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for meeting_recording_registrants
+  # List Recording Registrants
+  # Cloud Recordings of past Zoom Meetings can be made [on-demand](https://support.zoom.us/hc/en-us/articles/360000488283-On-demand-Recordings). Users should be [registered](https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/meetingrecordingregistrantcreate) to view these recordings.  Use this API to list registrants of **On-demand Cloud Recordings** of a past meeting.<br> **Scopes:** `recording:read:admin`, `recording:read`.<br>   
+  # @param meeting_id The meeting ID.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :status The registrant status:<br>`pending` - Registrant's status is pending.<br>`approved` - Registrant's status is approved.<br>`denied` - Registrant's status is denied.
+  # @option opts [Integer] :page_size The number of records returned within a single API call.
+  # @option opts [Integer] :page_number The current page number of returned records.
+  # @return [RegistrationList1]
+  describe 'meeting_recording_registrants test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_delete
+  # Delete Meeting Recordings
+  # Delete all recording files of a meeting.<br><br>  **Scopes:** `recording:write:admin` `recording:write`<br> <br> **Prerequisites**: * Cloud Recording should be enabled on the user's account.<br> 
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :action The recording delete actions:<br>`trash` - Move recording to trash.<br>`delete` - Delete recording permanently.
+  # @return [nil]
+  describe 'recording_delete test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_delete_one
+  # Delete a Meeting Recording File
+  # Delete a sprecific recording file from a meeting.<br><br> **Scopes**: `recording:write:admin` `recording:write`<br>  <br>
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param recording_id The recording ID.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :action The recording delete actions:<br>`trash` - Move recording to trash.<br>`delete` - Delete recording permanently.
+  # @return [nil]
+  describe 'recording_delete_one test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_get
+  # Get Meeting Recordings
+  # Get all the [recordings](https://support.zoom.us/hc/en-us/articles/203741855-Cloud-Recording#h_7420acb5-1897-4061-87b4-5b76e99c03b4) from a meeting.<br><br> **Scopes:** `recording:read:admin` `recording:read`<br>    
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param [Hash] opts the optional parameters
+  # @return [Object]
+  describe 'recording_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_registrant_question_update
+  # Update Registration Questions
+  # For [on-demand](https://support.zoom.us/hc/en-us/articles/360000488283-On-demand-Recordings) meeting recordings, you can include fields with questions that will be shown to registrants when they register to view the recording.  Use this API to update registration questions that are to be answered by users while registering to view a recording.<br> **Scopes:** `recording:write:admin`, `recording:write`<br> <br> 
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param body Recording Registrant Questions
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'recording_registrant_question_update test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_registrants_questions_get
+  # Get Registration Questions
+  # For [on-demand](https://support.zoom.us/hc/en-us/articles/360000488283-On-demand-Recordings) meeting recordings, you can include fields with questions that will be shown to registrants when they register to view the recording.  Use this API to retrieve a list of questions that are displayed for users to complete when registering to view the recording of a specific meeting.<br> **Scopes:** `recording:read:admin`, `recording:read`<br>    
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param [Hash] opts the optional parameters
+  # @return [RecordingRegistrantQuestions]
+  describe 'recording_registrants_questions_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_setting_update
+  # Get Meeting Recording Settings
+  # Retrieve settings applied to a meeting's [Cloud Recording](https://support.zoom.us/hc/en-us/articles/203741855-Cloud-Recording).<br><br> **Scopes**: `recording:read:admin` `recording:read`<br>  <br>
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param [Hash] opts the optional parameters
+  # @return [RecordingSettings]
+  describe 'recording_setting_update test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_settings_update
+  # Update Meeting Recording Settings
+  # Update settings applied to a meeting's [Cloud Recording](https://support.zoom.us/hc/en-us/articles/203741855-Cloud-Recording)<br><br> **Scopes**: `recording:write:admin` `recording:write`<br>  <br>
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param body Meeting recording Settings
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'recording_settings_update test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_status_update
+  # Recover Meeting Recordings
+  # Zoom allows users to recover recordings from trash for up to 30 days from the deletion date. Use this API to recover all deleted [Cloud Recordings](https://support.zoom.us/hc/en-us/articles/203741855-Cloud-Recording) of a specific meeting.<br><br> **Scopes**: `recording:write:admin` `recording:write`<br>  <br> **Prerequisites**:<br> * A Pro user with Cloud Recording enabled.
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param body 
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'recording_status_update test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recording_status_update_one
+  # Recover a Single Recording
+  # Zoom allows users to recover recordings from trash for up to 30 days from the deletion date. Use this API to recover a single recording file from the meeting.<br> **Scopes:** `recording:write:admin` `recording:write`<br>  <br> 
+  # @param meeting_id The meeting ID or meeting UUID. If the meeting ID is provided instead of UUID,the response will be for the latest meeting instance. If a UUID starts with \"/\" or contains \"//\" (example: \"/ajXp112QmuoKj4854875==\"), you must **double encode** the UUID before making an API request. 
+  # @param recording_id The recording ID.
+  # @param body 
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'recording_status_update_one test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for recordings_list
+  # List All Recordings
+  # When a user records a meeting by choosing the **Record to the Cloud** option, the video, audio, and chat text are recorded in the Zoom cloud.   Use this API to list all [Cloud recordings](https://support.zoom.us/hc/en-us/articles/203741855-Cloud-Recording) of a user.<br><br> **Scopes:** `recording:read:admin` `recording:read`<br>  <br> **Prerequisites:**  * Pro or a higher plan. * Cloud Recording must be enabled on the user's account.
+  # @param user_id The user ID or email address of the user. For user-level apps, pass `me` as the value for userId.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :page_size The number of records returned within a single API call.
+  # @option opts [String] :next_page_token The next page token is used to paginate through large result sets. A next page token will be returned whenever the set of available results exceeds the current page size. The expiration period for this token is 15 minutes.
+  # @option opts [String] :mc Query Metadata of Recording if an On-Premise Meeting Connector was used for the meeting.
+  # @option opts [BOOLEAN] :trash Query trash. `true`: List recordings from trash.<br> `false`: Do not list recordings from the trash.<br> The default value is `false`. If you set it to `true`, you can use the `trash_type` property to indicate the type of Cloud recording that you need to retrieve. 
+  # @option opts [Date] :from Start date in 'yyyy-mm-dd' format. (Within 6 month range)
+  # @option opts [Date] :to End date in 'yyyy-mm-dd' format. (Within 6 month range)
+  # @option opts [String] :trash_type The type of Cloud recording that you would like to retrieve from the trash. The value can be one of the following:<br>     `meeting_recordings`: List all meeting recordings from the trash.<br>     `recording_file`: List all individual recording files from the trash. 
+  # @return [RecordingList]
+  describe 'recordings_list test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/common_area_phones_api_spec.rb

@@ -0,0 +1,97 @@
+=begin
+#Zoom API
+
+#The Zoom API allows developers to safely and securely access information from Zoom. You can use this API to build private services or public applications on the [Zoom App Marketplace](http://marketplace.zoom.us). To learn how to get your credentials and create private/public applications, read our [Authorization Guide](https://marketplace.zoom.us/docs/guides/authorization/credentials). All endpoints are available via `https` and are located at `api.zoom.us/v2/`.  For instance you can list all users on an account via `https://api.zoom.us/v2/users/`.
+
+OpenAPI spec version: 2.0.0
+Contact: developersupport@zoom.us
+Generated by: https://github.com/swagger-api/swagger-codegen.git
+Swagger Codegen version: 2.4.12
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for ZoomUs::CommonAreaPhonesApi
+# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
+# Please update as you see appropriate
+describe 'CommonAreaPhonesApi' do
+  before do
+    # run before each test
+    @instance = ZoomUs::CommonAreaPhonesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of CommonAreaPhonesApi' do
+    it 'should create an instance of CommonAreaPhonesApi' do
+      expect(@instance).to be_instance_of(ZoomUs::CommonAreaPhonesApi)
+    end
+  end
+
+  # unit tests for add_common_area_phone
+  # Add a Common Area Phone
+  # A common area phone can be provisioned by a Zoom account owner or a Zoom admin so that anyone in an organization can use it. For example, if your office has shared desks that don't belong to a specific employees, you could add a common area phone so that any person can use it.<br> Use this API to [add a common area phone](https://support.zoom.us/hc/en-us/articles/360028516231-Managing-Common-Area-Phones#h_2d0da347-c35a-4993-9771-e21aaa568deb).<br><br> **Prerequisites:**<br> * Pro or a higher account with Zoom Phone license. * Account owner or admin permissions. * [Supported device](https://support.zoom.us/hc/en-us/articles/360001299063-Zoom-Voice-Supported-Devices)<br> **Scope:** `phone:write:admin`<br>     
+  # @param [Hash] opts the optional parameters
+  # @option opts [Body74] :body 
+  # @return [InlineResponse20124]
+  describe 'add_common_area_phone test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for delete_common_area_phone
+  # Delete a Common Area Phone
+  # A common area phone can be provisioned by a Zoom account owner or a Zoom admin so that anyone in an organization can use it. For example, if your office has shared desks that don't belong to a specific employees, you could add a common area phone so that any person can use it.<br> Use this API to remove the [common area phone](https://support.zoom.us/hc/en-us/articles/360028516231-Managing-Common-Area-Phones) from Zoom Phone System in an account.<br><br>**Prerequisites:**<br> * Pro or a higher account with Zoom Phone license. * Account owner or admin permissions. * [Supported device](https://support.zoom.us/hc/en-us/articles/360001299063-Zoom-Voice-Supported-Devices)<br> **Scopes:** `phone:write:admin`<br>   
+  # @param common_area_phone_id Unique Identifier of the common area phone.
+  # @param [Hash] opts the optional parameters
+  # @return [Object]
+  describe 'delete_common_area_phone test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_a_common_area_phone
+  # Get Common Area Phone Details
+  # A common area phone can be provisioned by a Zoom account owner or a Zoom admin so that anyone in an organization can use it. For example, if your office has shared desks that don't belong to a specific employees, you could add a common area phone so that any person can use it.<br> Use this API to get details on a specific [common area phone](https://support.zoom.us/hc/en-us/articles/360028516231-Managing-Common-Area-Phones) in an account.<br><br>**Prerequisites:**<br> * Pro or a higher account with Zoom Phone license. * Account owner or admin permissions. * [Supported device](https://support.zoom.us/hc/en-us/articles/360001299063-Zoom-Voice-Supported-Devices)<br> **Scopes:** `phone:read:admin`<br>   
+  # @param common_area_phone_id Unique Identifier of the Common Area Phone. This can be retrieved from List Common Area Phones API.
+  # @param [Hash] opts the optional parameters
+  # @return [InlineResponse20096]
+  describe 'get_a_common_area_phone test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_common_area_phones
+  # List Common Area Phones
+  # A common area phone can be provisioned by a Zoom account owner or a Zoom admin so that anyone in an organization can use it. For example, if your office has shared desks that don't belong to a specific employees, you could add a common area phone so that any person can use it.<br> Use this API to [list all common area phone](https://support.zoom.us/hc/en-us/articles/360028516231-Managing-Common-Area-Phones) in an account.<br><br>**Prerequisites:**<br> * Pro or a higher account with Zoom Phone license. * Account owner or admin permissions. * [Supported device](https://support.zoom.us/hc/en-us/articles/360001299063-Zoom-Voice-Supported-Devices)<br><br> **Scope:** `phone:read:admin`<br>   
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :page_size The total number of records returned from a single API call.
+  # @option opts [String] :next_page_token The next page token is used to paginate through large result sets. A next page token will be returned whenever the set of available results exceeds the current page size. The expiration period for this token is 15 minutes.
+  # @return [InlineResponse20095]
+  describe 'list_common_area_phones test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for update_common_area_phone
+  # Update Common Area Phone
+  # A common area phone can be provisioned by a Zoom account owner or a Zoom admin so that anyone in an organization can use it. For example, if your office has shared desks that don't belong to a specific employees, you could add a common area phone so that any person can use it.<br> Use this API to update details on a specific [common area phone](https://support.zoom.us/hc/en-us/articles/360028516231-Managing-Common-Area-Phones) in an account.<br><br>**Prerequisites:**<br> * Pro or a higher account with Zoom Phone license. * Account owner or admin permissions. * [Supported device](https://support.zoom.us/hc/en-us/articles/360001299063-Zoom-Voice-Supported-Devices)<br> **Scopes:** `phone:write:admin`<br>   
+  # @param common_area_phone_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Body75] :body 
+  # @return [Object]
+  describe 'update_common_area_phone test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end