Access Claude Compliance Data in Mule Applications Using the CData JDBC Driver

The CData JDBC Driver for Claude Compliance connects Claude Compliance data to Mule applications enabling read functionality with familiar SQL queries. The JDBC Driver allows users to easily create Mule applications to backup, transform, report, and analyze Claude Compliance data.

This article demonstrates how to use the CData JDBC Driver for Claude Compliance inside of a Mule project to create a Web interface for Claude Compliance data. The application created allows you to request Claude Compliance data using an HTTP request and have the results returned as JSON. The exact same procedure outlined below can be used with any CData JDBC Driver to create a Web interface for the hundreds of available data sources.

1. Create a new Mule Project in Anypoint Studio.
2. Add an HTTP Connector to the Message Flow.
3. Configure the address for the HTTP Connector.
4. Add a Database Select Connector to the same flow, after the HTTP Connector.
5. Create a new Connection (or edit an existing one) and configure the properties.
   • Set Connection to "Generic Connection"
   • Select the CData JDBC Driver JAR file in the Required Libraries section (e.g. cdata.jdbc.claudecompliance.jar).
   • Set the URL to the connection string for Claude Compliance

     The driver connects to Claude Compliance using a Compliance Access Key, the only supported authentication method. Set the following connection property:

     • APIKey: The Compliance Access Key you created.

     Creating a Compliance Access Key

     1. Enable the Compliance API for your organization.
     2. Sign in to claude.ai as a primary owner or organization owner and open Organization settings > API > Keys.
     3. Select Create Key and assign only the scopes your integration needs:
        • read:compliance_activities for Activities and the typed activity views.
        • read:compliance_org_data for organizations, roles, groups, and settings.
        • read:compliance_user_data for users, chats, files, projects, and downloads.
        • delete:compliance_user_data for the explicit Delete stored procedures.
     4. Create the key and copy it when it appears. The key starts with sk-ant-api01- and is shown only once.

     Optionally, set OrganizationUUID to limit organization-scoped views (such as OrganizationUsers and ComplianceRoles) to a single linked organization. If it is left empty, those views default to the first available organization and do not include data from all linked organizations.

     Built-in Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the Claude Compliance JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     
     		java -jar cdata.jdbc.claudecompliance.jar
     		

     Fill in the connection properties and copy the connection string to the clipboard.

   • Set the Driver class name to cdata.jdbc.claudecompliance.ClaudeComplianceDriver.
   • Click Test Connection.
6. Set the SQL Query Text to a SQL query to request Claude Compliance data. For example:

   SELECT Id, Name FROM Projects WHERE OrganizationUuid = 'abcdef01-2345-6789-abcd-ef0123456789'

   
7. Add a Transform Message Component to the flow.
8. Set the Output script to the following to convert the payload to JSON:

   %dw 2.0
   output application/json
   ---
   payload
           

   
9. To view your Claude Compliance data, navigate to the address you configured for the HTTP Connector (localhost:8081 by default): http://localhost:8081. The Claude Compliance data is available as JSON in your Web browser and any other tools capable of consuming JSON endpoints.

At this point, you have a simple Web interface for working with Claude Compliance data (as JSON data) in custom apps and a wide variety of BI, reporting, and ETL tools. Download a free, 30 day trial of the JDBC Driver for Claude Compliance and see the CData difference in your Mule Applications today.