Please enable JavaScript to view this site.

Zoom Forums

Zoom API Data Model

Navigation: Schema: Billing > Tables

postAccountsByAccountId_Plan_large_meetingPlans

Subscribe plans for a sub accountSubscribe plans for a sub account of the master account <aside>Can only subscribe plans for the sub account which is a free account and paid by master account</aside>

Catalog: Zoom

Schema: Billing

This is a read-only table function. The Zoom API may not support changing the data or the Invantive SQL driver for Zoom does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Zoom API.

Select Zoom API URL: /accounts/{accountId}/plans

Insert Zoom API URL: /accounts/{accountId}/plans

Update Zoom API URL: /accounts/{accountId}/plans

Delete Zoom API URL: /accounts/{accountId}/plans

Field Selection Method: NotRequired

Base Path: plan_large_meeting[*]

Select Zoom API Operation: post /accounts/{accountId}/plans

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function postAccountsByAccountId_Plan_large_meetingPlans. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be treated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example with `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name

Data Type

Required

Default Value

Documentation

accountId

string

☑

 

The account ID

body

string

☑

 

 

 

Table Function Columns

The columns of the table function postAccountsByAccountId_Plan_large_meetingPlans are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

hosts

int64

 

☐

Account plan number of hosts

plan_audio_callout_countries

string

 

☐

Call-out countries, multiple value separated by comma

plan_audio_ddi_numbers

int64

 

☐

Dedicated Dial-In Numbers

plan_audio_premium_countries

string

 

☐

Premium countries, multiple value separated by comma

plan_audio_tollfree_countries

string

 

☐

Toll-free countries, multiple value separated by comma

plan_audio_type

string

 

☐

Additional Audio Conferencing <a href="#plans">plan type</a>

plan_base_hosts

int64

 

☑

Account base plan number of hosts. For a Pro Plan, please select a value between 1 and 9. For a Business Plan, please select a value between 10 and 49. For a Education Plan, please select a value between 20 and 149. For a Free Trial Plan, please select a value between 1 and 9999.

plan_base_type

string

 

☑

Account base <a href="#plans">plan type</a>

plan_recording

string

 

☐

Additional Cloud Recording Plan

plan_room_connector_hosts

int64

 

☐

Account plan number of hosts

plan_room_connector_type

string

 

☐

Account <a href="#plans">plan type</a>

plan_zoom_rooms_hosts

int64

 

☐

Account plan number of hosts

plan_zoom_rooms_type

string

 

☐

Account <a href="#plans">plan type</a>

RESULT

string

 

☐

Outcome of operation as single plain text column.

type

string

 

☐

Account <a href="#plans">plan type</a>

 

16-06-2022 17:21 Version 22.1.46-BETA+3385

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer