SQL Driver for Chargebee Chargebee is cloud software for subscription invoicing and payment by SaaS-companies. The Chargebee driver covers 114 tables and 1534 columns. ## Chargebee API Clients Invantive UniversalSQL is available on many user interfaces ("clients" in traditional server-client paradigma). All Invantive UniversalSQL statements can be exchanged with a close to 100% compatibility across all clients and operating systems (Windows, MacOS, Linux, iOS, Android). The clients include Microsoft Excel, Microsoft Power BI, Microsoft Power Query, Microsoft Word and Microsoft Outlook. Web-based clients include Invantive Cloud, Invantive Bridge Online as OData proxy, Invantive App Online for interactive apps, Online SQL Editor for query execution and Invantive Data Access Point as extended proxy. The For technical users there are command-line editions of Invantive Data Hub running on iOS, Android, Windows, MacOS and Linux. Invantive Data Hub is also often used for enterprise server applications such as ETL. High-volume replication of data taken from the Chargebee API into traditional databases such as SQL Server (on-premises and Azure), MySQL, PostgreSQL and Oracle is possible using Finally, online web apps can be build for Chargebee using App Online of ## Monitor API Calls When a query or DML-statement has been executed on Invantive UniversalSQL a developer can evaluate the actual calls made to the Chargebee API using a query on sessionios@DataDictionary. As an alternative, extensive request and response logging can be enabled by setting log-native-calls-to-disk to true. In the %USERPROFILE%\Invantive\NativeLog folder Invantive UniversalSQL will create log files per Chargebee API request and response. ## Specifications The SQL driver for Chargebee does not support partitioning. Define one data container in a database for each company in Chargebee to enable parallel access for data from multiple companies. An introduction into the concepts of Invantive UniversalSQL such as databases, data containers and partitioning can be found in the The configuration can be changed using various attributes from the database definition, on log on and during use. A full list of configuration options is listed in the The catalog name is used to compose the full qualified name of an object like a table or view. The schema name is used to compose the full qualified name of an object like a table or view. On Chargebee the comparison of two texts is case sensitive by default. Changes and bug fixes on the Chargebee SQL driver can be found in the The driver has the following properties: - Driver code for use in settings.xml: ``Chargebee`` - Alias: ``cbe`` - Recommended alias: ``cbe`` Driver code for use in settings.xml General documentation on Chargebee is available at Authentication Authentication is done using an API key. An API key can be found and/or registered on https://SERVER/apikeys_and_webhooks/api. The API key is valid for a specific site. The Chargebee API key can be configured in settings.xml as the value of defaultPassword attribute of the database element. The site is derived from the connection string attribute 'server'. Beware that after deleting records, Chargebee can still return those records for some time (at least 5 seconds). Updated 10-06-2024 18:44 using Invantive UniversalSQL version 24.1.3-BETA+4689. 10-06-2024 18:44 Version 24.1.3-BETA+4689 ## Objects Per object category a list is available: - [[Tables]] - [[Procedures]]