New message text here

Hmm, I don't know enough to give you a confident answer yet. Please provide more information about your issue or question related to Airbyte, and I'll do my best to help you based on the information extracts I have. In the meantime, you can also check the [Airbyte documentation](https://docs.airbyte.com) for more information.

Yes, you can view the outgoing HTTP requests made by the connector in the Connector Builder UI's testing panel. Here's how to access it: 1. Open the Connector Builder UI. 2. In the testing panel, you'll find several tabs. 3. Click on the Request tab. This tab displays the outgoing HTTP request made by the connector to retrieve the selected page of data, which can be useful for debugging. For more information on how to use the Connector Builder UI and its testing panel, please refer to the [Connector Builder UI documentation](https://docs.airbyte.com/connector-development/config-based/connector-builder-ui#connector-builder-testing-panel).

I apologize for the confusion earlier. Based on the information extracts I have, you can view the outgoing requests and their associated responses by running the

read

operation with the

--debug

flag. Here's an example command:

bash python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json --debug

This command will print out debug information, including the outgoing request and its associated response, which can help you investigate the issue with your OAuth authentication setup. For more details, refer to the [reading data tutorial](https://docs.airbyte.com/connector-development/config-based/tutorial/reading-data#part-1).

You should execute the command in the directory where your connector's

main.py

file is located. This is typically the root directory of your connector's source code. For example, if you're working on a custom connector, the directory would be something like

airbyte-integrations/connectors/source-your-connector-name

. Here's the command again for reference:

bash python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json --debug

Make sure to replace

source-your-connector-name

with the actual name of your connector.

To find the correct directory for the connector you are developing, follow these steps: 1. First, locate the root directory of the Airbyte project on your local machine. This is the directory where you cloned the Airbyte repository. 2. Next, navigate to the

airbyte-integrations

directory within the Airbyte project root:

cd airbyte-integrations

3. Inside the

airbyte-integrations

directory, you'll find the

connectors

directory. Navigate to it:

cd connectors

4. In the

connectors

directory, you should see multiple subdirectories with names like

source-connector-name

or

destination-connector-name

. Find the one that corresponds to the connector you are developing. For example, if you're working on a custom source connector named

my-custom-source

, the directory would be

source-my-custom-source

. Navigate to that directory:

cd source-my-custom-source

Now you are in the correct directory for the connector you are developing. You can execute the command mentioned earlier in this directory:

bash python main.py read --config secrets/config.json --catalog integration_tests/configured_catalog.json --debug

Make sure to replace the

config.json

and

configured_catalog.json

file paths with the correct paths for your connector's configuration and catalog files.

I will make sure this issue is considered for the next development iteration

Could you show your authentication config?

I can try to help getting it working

hmm, actually reading through https://developers.zoom.us/docs/api/rest/using-zoom-apis/ (I suspect this is what you are working with) it seems like zoom is only supporting the client credentials flow which is not supported in the low code cdk today: https://github.com/airbytehq/airbyte/issues/23450

ah, wait, I just checked the code and this won't work

The set grant type can't be overwritten this way: https://github.com/airbytehq/airbyte/blob/ec9707c71ff59b595a373c5b12b82174602cd03b[…]cdk/sources/streams/http/requests_native_auth/abstract_oauth.py

So for now you either switch to the yaml view where you can set the

grant_type

on the authenticator, roll back to the previous version of Airbyte, or use another authenticaton type. Sorry for the hassle. I will raise this with the team today so we can fix it quickly