GoToWebinar
Building the JDBC URL
After installing the license, open the connection management page by running java -jar kingswaysoft.jdbc.jar. Enter the required details to generate the JDBC connection URL. Click Test Connection to test the generated URL, or Copy to Clipboard to copy the connection string for use in your application.
Note: If the license is not installed, you can still use the connection manager to generate a JDBC URL; however, the Test Connection feature will be disabled.
General Page
The General page allows you to specify connection properties and login credentials for the GoToWebinar REST service.

General Settings
- API Throttling Rate
-
The API Throttling Rate will limit the number of requests that can be sent per minute. Set this value to 0 to disable API throttling.
Token File Details
After a valid token file is selected, the Organizer Key and Account Key are displayed for your reference.
- Organizer Key
-
A GoToWebinar Organizer Key is a unique, numeric identifier for a user account.
- Account Key
-
A GoToWebinar account key is a unique identifier required for API operations.
Authentication Methods for GoToWebinar
OAuth Authorization Code
Use a saved token file along with its token password to establish a connection. To generate a new token file, click Generate Token File and follow the on-screen process. After saving the token file locally, enter the token password to connect.
- Generate Token File
-
This button completes the OAuth authentication process to generate a new access token.
- Client Key: The Client Key option allows you to specify the unique ID which identifies the application making the request.
- Client Secret: The Client Secret option allows you to specify the client secret belonging to your app.
- Redirect URL: The Redirect URL option allows you to specify the Redirect URL to complete the authentication process.
- Path to Token File
-
The path to the token file on the file system.
- Token File Password
-
The password of the token file.
Personal Access Token
Use a saved token file along with its token password to establish a connection. To generate a new token file, click Generate Token File and follow the on-screen process. After saving the token file locally, enter the token password to connect.
- Generate Token File
-
This button completes the OAuth authentication process to generate a new access token.
- Client Key: The Client Key option allows you to specify the unique ID which identifies the application making the request.
- Client Secret: The Client Secret option allows you to specify the client secret belonging to your app.
- Personal Access Token: The Personal Access Token of the user to use when generating the token.
- Path to Token File
-
The path to the token file on the file system.
- Token File Password
-
The password of the token file.
After completing the configuration for all required connection and authentication settings in the JDBC Connection Manager, you can use the Test Connection button to validate your configuration and verify API requests will authenticate successfully.
Advanced Settings Page

Proxy Server Settings
The Advanced Settings page allows you to specify advanced settings for the connection.
- Proxy Mode
-
The Proxy Mode option allows you to specify how you want to configure the proxy server setting. There are three options available.
- No Proxy
- Auto-detect (Use system configured proxy)
- Manual
- Proxy Server
-
Using the Proxy Server option allows you to specify the name of the proxy server for the connection.
- Port
-
The Port option allows you to specify the port number of the proxy server for the connection.
- Username (Proxy Server Authentication)
-
The Username option (under Proxy Server Authentication) allows you to specify the proxy user account.
- Password (Proxy Server Authentication)
-
The Password option (under Proxy Server Authentication) allows you to specify the proxy user's password.
Miscellaneous Settings
- Timeout (secs)
-
The Timeout (secs) option allows you to specify a timeout value in seconds for the connection. The default value is 120 seconds. Specify 0 for infinite timeout.
- Retry on Intermittent Errors
-
The retry on intermittent errors determines if requests will be retried when there is an error. If this option is checked requests will be retried up to 3 times.
- Ignore Certificate Errors
-
This option can be used to ignore those SSL certificate errors when connecting to the target server.
Warning: Enabling the "Ignore Certificate Errors" option is generally NOT recommended, particularly for production instances. Unless there is a strong reason to believe the connection is secure - such as the network communication is only happening in an internal infrastructure, this option should be unchecked for best security.
Note: When this option is enabled, it applies to all HTTP-based SSL connections in the same job process.
- Concurrent Writing Threads
-
This option can be used to set the number of threads to be used during write operations. This can improve performance during large-volume write operations.
Using the JDBC Driver
This section provides examples that use JDBC classes such as Connection, Statement, and ResultSet to manage interactions with GoToWebinar data. It covers regular statements and prepared statements for complex or frequently executed queries.
Executing Statements
After you have connected from your code, you can execute SQL statements using the Statement class. For connection details, see Connecting with DriverManager or Connecting with DataSource. For parameterized statements, see Executing Prepared Statements.
SELECT
Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data. To retrieve the results of a query, call the getResultSet method of the Statement.
String sql = "SELECT * FROM recordingassets/search WHERE accountKey = '123' ORDER BY createTime DESC"; try { ResultSet resultSet = statement.executeQuery(sql); LOGGER.info(resultSet.toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
INSERT
Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "INSERT INTO webinars (subject, times) VALUES " + "('testSubject', '[{\"startTime\": \"2026-03-13T10:00:00Z\", \"endTime\": \"2026-03-13T22:00:00Z\"}]')"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors
1d3d16b6-a813-4ebe-a11d-08699d17e03e,null,null,{"subject":"testSubject","times":[{"startTime":"2026-03-13T10:00:00Z","endTime":"2026-03-13T22:00:00Z"}]},false
UPDATE
Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.
String sql = "UPDATE webinars SET subject = 'UpdatedSubject' WHERE webinarKey = 4805163135186390871"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors
null,null,null,{"subject":"UpdatedSubject"},false
DELETE
Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "DELETE FROM webinars/coorganizers WHERE webinarKey = '4805163135186390871' AND coorganizerKey = '123456789'"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors null,null,null,null,false
Executing Prepared Statements
Using a PreparedStatement can improve performance when you need to execute a SQL statement multiple times with different parameters. Unlike a Statement object, a PreparedStatement object is provided with a SQL statement when it is created, which can then be executed with different values each time. This special type of statement is derived from the more general Statement class.
Below are the steps outlining how to execute a prepared statement:
Creating and Executing a Prepared Statement
- Create a PreparedStatement
-
Use the
prepareStatementmethod of theConnectionclass to instantiate aPreparedStatement.For connection details, see Connecting with DriverManager or Connecting with DataSource.
- Set Parameters
- Declare parameters by calling the corresponding setter method of the
PreparedStatement. - NOTE: The parameter indices start at 1.
- Execute the PreparedStatement
- Use the generic
executeorexecuteUpdatemethod of thePreparedStatement. - Retrieve Results
- Call the
getResultSetmethod of thePreparedStatementto obtain the query results, which are returned as aResultSet. - Iterate Over the Result Set
- Use the
nextmethod of theResultSetto iterate through the results. To obtain column information, use theResultSetMetaDataclass. Instantiate aResultSetMetaDataobject by calling thegetMetaDatamethod of theResultSet.
SELECT
Use the PreparedStatement class's generic execute method or the executeQuery method to execute SQL statements that return data.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the retrieved data.
String sql = "SELECT * FROM webinars WHERE webinarKey = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "1205515997588226907"); boolean ret = ps.execute(sql); if (ret) { ResultSet rs = ps.getResultSet(); LOGGER.info(rs.toString()); } } catch (SQLException e) { LOGGER.severe(e.toString()); }
INSERT
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an INSERT operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of inserted data, exceptions raised during execution, and the data affected by the insertion.
String sql = "INSERT INTO webinars (subject, times) VALUES (?, ?)"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "testSubject"); ps.setString(2, "[{\"startTime\": \"2026-03-13T10:00:00Z\", \"endTime\": \"2026-03-13T22:00:00Z\"}]"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors
1d3d16b6-a813-4ebe-a11d-08699d17e03e,null,null,{"subject":"testSubject","times":[{"startTime":"2026-03-13T10:00:00Z","endTime":"2026-03-13T22:00:00Z"}]},false
UPDATE
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an UPDATE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of updated data, exceptions raised during execution, and the data affected by the update.
String sql = "UPDATE webinars SET subject = ? WHERE webinarKey = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "UpdatedSubject"); ps.setString(2, "4805163135186390871"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors
null,null,null,{"subject":"UpdatedSubject"},false
DELETE
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute a DELETE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.
String deleteSql = "DELETE FROM webinars/coorganizers WHERE webinarKey = ? AND coorganizerKey = ?"; try { PreparedStatement ps = connection.prepareStatement(deleteSql); ps.setString(1, "4805163135186390871"); ps.setString(2, "123456789"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { e.printStackTrace(); }
id,errorcode,errormessage,processdata,haserrors null,null,null,null,false
Metadata Discovery
This section provides examples on how to retrieve table and column metadata using the getTables, getColumns, and getPrimaryKeys methods from the DatabaseMetaData interface. These are essential for discovering database structures.
Tables
The getTables method from the DatabaseMetaData interface can be used to retrieve a list of tables.
This method only retrieves tables that are not write-only.
To get a list of tables that includes write-only tables, query the table system.tables.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet rs = connection.getMetaData().getTables(null, null, null, null); LOGGER.info("\r\n" + rs.toString()); } catch (SQLException e) { LOGGER.severe(e.getMessage()); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,TABLE_TYPE,REMARKS,TYPE_CAT,TYPE_SCHEM,TYPE_NAME,SELF_REFERENCING_COL_NAME,REF_GENERATION null,null,userSubscriptions,TABLE,null,null,null,null,null,null null,null,webhooks,TABLE,null,null,null,null,null,null null,null,webinars,TABLE,null,null,null,null,null,null null,null,webinars/attendees,TABLE,null,null,null,null,null,null null,null,webinars/audio,TABLE,null,null,null,null,null,null null,null,webinars/coorganizers,TABLE,null,null,null,null,null,null null,null,webinars/meetingtimes,TABLE,null,null,null,null,null,null null,null,webinars/panelists,TABLE,null,null,null,null,null,null null,null,webinars/performance,TABLE,null,null,null,null,null,null null,null,webinars/recordingAssets,TABLE,null,null,null,null,null,null ......
The getTables method returns the following metadata columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The catalog that contains the table. |
| TABLE_SCHEM | String | The schema of the table. |
| TABLE_NAME | String | The name of the table. |
| TABLE_TYPE | String | The type of the table (e.g., TABLE or VIEW). |
| REMARKS | String | An optional description of the table. |
Columns
Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns.
This method returns columns only for tables that are not write-only.
To get columns for write-only tables, query the table system.columns.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet rs = connection.getMetaData().getColumns(null, null, "webinars", null); LOGGER.info(rs.toString()); } catch (SQLException e) { e.printStackTrace(); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,DATA_TYPE,TYPE_NAME,COLUMN_SIZE,BUFFER_LENGTH,DECIMAL_DIGITS,NUM_PREC_RADIX,NULLABLE,REMARKS,COLUMN_DEF,SQL_DATA_TYPE,SQL_DATETIME_SUB,CHAR_OCTET_LENGTH,ORDINAL_POSITION,IS_NULLABLE,SCOPE_CATALOG,SCOPE_SCHEMA,SCOPE_TABLE,SOURCE_DATA_TYPE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE null,null,webinars,accountKey,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,webinars,approvalType,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,webinars,breakoutsAllowed,16,BOOLEAN,null,null,0,0,null,null,null,16,null,null,null,null,null,null,null,null,null,null,DT_BOOL null,null,webinars,broadcast,16,BOOLEAN,null,null,0,0,null,null,null,16,null,null,null,null,null,null,null,null,null,null,DT_BOOL null,null,webinars,deniedRegistrants,-5,BIGINT,null,null,0,0,null,null,null,-5,null,null,null,null,null,null,null,null,null,null,DT_I8 null,null,webinars,description,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR null,null,webinars,experienceType,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR ......
The getColumns method returns the following columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The database name. |
| TABLE_SCHEM | String | The table schema. |
| TABLE_NAME | String | The table name. |
| COLUMN_NAME | String | The column name. |
| DATA_TYPE | Integer | The data type represented by a constant value from java.sql.Types. |
| TYPE_NAME | String | The data type name used by the driver. |
| COLUMN_SIZE | Integer | The length in characters of the column or the numeric precision. |
| BUFFER_LENGTH | Integer | The buffer length. |
| DECIMAL_DIGITS | Integer | The column scale or number of digits to the right of the decimal point. |
| NUM_PREC_RADIX | Integer | The radix, or base. |
| NULLABLE | Integer | Whether the column can contain null as defined by the following JDBC DatabaseMetaData constants: columnNoNulls (0) or columnNullable (1). |
| REMARKS | String | The comment or note associated with the object. |
| COLUMN_DEF | String | The default value for the column. |
| SQL_DATA_TYPE | Integer | Reserved by the specification. |
| SQL_DATETIME_SUB | Integer | Reserved by the specification. |
| CHAR_OCTET_LENGTH | Integer | The maximum length of binary and character-based columns. |
| ORDINAL_POSITION | Integer | The position of the column in the table, starting at 1. |
| IS_NULLABLE | String | Whether a null value is allowed: YES or NO. |
| SCOPE_CATALOG | String | The catalog of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SCOPE_SCHEMA | String | The schema of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SCOPE_TABLE | String | The name of the table referenced by a reference attribute (null if DATA_TYPE is not REF). |
| SOURCE_DATA_TYPE | Short | The source type of a distinct type or user-defined REF type (null if DATA_TYPE is neither DISTINCT nor a user-defined REF). |
| IS_AUTOINCREMENT | String | Whether the column value is assigned by GoToWebinar in fixed increments. |
| IS_GENERATEDCOLUMN | String | Whether the column is generated: YES or NO. |
| DTS_TYPE | String | Object DTS attribute type. |
Primary Keys
The getPrimaryKeys method in the DatabaseMetaData interface is used to retrieve metadata about primary keys for a given table in GoToWebinar.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet resultSet = connection.getMetaData().getPrimaryKeys(null, null, "webinars"); LOGGER.info("\r\n" + resultSet.toString()); } catch (SQLException e) { LOGGER.severe(e.getMessage()); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,KEY_SEQ,PK_NAME null,null,webinars,webinarKey,1,null
The getPrimaryKeys method returns the following columns:
| Column Name | Data Type | Description |
|---|---|---|
| TABLE_CAT | String | The name of the catalog (if it exists) that the table is located within. |
| TABLE_SCHEM | String | The schema or namespace of the table (if it exists) for the specified table. |
| TABLE_NAME | String | The name of the table that contains the primary key. |
| COLUMN_NAME | String | The name of the column that serves as the primary key for the table. |
| KEY_SEQ | Short | The position of the column within the primary key. If the table has a single column as the primary key, KEY_SEQ will always be 1. |
| PK_NAME | String | The name of the primary key. |
Connection Settings
| Connection Setting | Type | Default Value | Description |
|---|---|---|---|
| AccountKey | String | "" | The GoToWebinar Account Key is a unique identifier required for API operations. |
| ApiThrottleRate | Integer | 60 | The maximum number of API requests a client can make to the server within a specific time period, defined in requests per minute. A value of 0 disables throttling. |
| CacheExpirationTime | Integer | 30 | Defines the expiration time for cache. A value of 0 disables caching. |
| ConcurrentWritingThreads | Integer | 1 | The number of threads for executing operations in parallel. A value of 0 will disable multi threading. |
| ConnectionTimeout | Integer | 30 | ConnectionTimeout is the maximum amount of time the program will wait to set up a connection to the GoToWebinar API. |
| IgnoreCertificateErrors | Boolean | false | Specifies whether to verify the certificate when connecting to GoToWebinar. If certificate verification is not required, you can set this value to 'true'. |
| ContinueOnErrors | Boolean | false | Determines if the program continues executing SQL statements after encountering an error. |
| LogFileSize | String | "10485760" | A string specifying the maximum size in bytes for a log file. |
| LogLevel | String | "INFO" | The logging level for the JDBC driver. |
| LogPath | String | "./jdbcLogs" | The directory where log files are stored. |
| OemKey | String | "" | The OEM license key. |
| OrganizerKey | String | "" | The GoToWebinar Organizer Key is a unique, numeric identifier for a user account. |
| PathToTokenFile | String | "" | The path to the token file. |
| ProxyMode | String | NoProxy | This setting configures the proxy. Allowed values are "NoProxy", "AutoDetect" and "Manual". |
| ProxyPassword | String | "" | The password to be used to authenticate to the proxy. |
| ProxyServer | String | "" | The host of the proxy server. |
| ProxyServerPort | Integer | 0 | The port of the proxy server. |
| ProxyUsername | String | "" | The username to be used to authenticate to the proxy. |
| ReadBatchSize | Integer | 100 | ReadBatchSize is used to set how many records can be read from GoToWebinar in a single call. |
| ResultPath | String | "" | The path where the execution result files are saved. |
| RetryOnIntermittentErrors | Boolean | true | The RetryOnIntermittentErrors parameter indicates whether to retry the connection when it might occasionally fail due to temporary issues. |
| SaveResult | Boolean | false | The SaveResult parameter indicates whether to save the execution results to a file. |
| ServiceName | String | "GoToWebinar" | The ServiceName refers to the name of the service API selected by the user. |
| ServiceTimeout | Integer | 120 | The ServiceTimeout is the timeout to receive the full response from GoToWebinar API. |
| Suppress404NotFoundError | Boolean | true | When set to true, if a query results in an HTTP 404 error, a result set will still be created. When set to false, an error is logged instead and no result set is created. |
| TokenPassword | String | "" | The password used to read the token file. |
| WriteBatchSize | Integer | 1 | WriteBatchSize is used to set how many records can be written to GoToWebinar in a single call. |