The knowledge sources don’t describe any way in Airbyte Cloud to see the
exact HTTP requests (URL, headers, body) that a connector is making, including for custom API connectors. They only cover higher‑level job logs and timelines, not low‑level request tracing. What you
can see today: 1.
Sync / job logs - For each sync, you can open the logs from the connection’s
Job History tab and click the three dots →
View logs. [[Browsing logs](
https://docs.airbyte.com/platform/operator-guides/browsing-output-logs)] - You can also
download the logs or
copy a link to the job from the same menu. [[Browsing logs](
https://docs.airbyte.com/platform/operator-guides/browsing-output-logs)] - These logs show connector activity and errors, but the docs do
not state that full HTTP requests (URLs, headers, bodies) are logged. 2.
Connection Timeline / Status - The
Connection Timeline shows events like syncs, schema updates, configuration changes, and links to jobs/logs, but not raw HTTP calls. [[Connection timeline](
https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/review-connection-timeline)] - The
Status page shows recent sync outcomes and high‑level error messages (rate limits, configuration errors, system errors), again without exposing raw HTTP requests. [[Connection status](
https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/review-connection-status#connection-troubleshooting)] There is also an open GitHub issue requesting exactly what you’re asking for: an option to log the actual HTTP calls (URL, cursor, headers, etc.) when debugging custom connectors, acknowledging that this is not currently available and would be a new feature. [[log http calls](
https://github.com/airbytehq/airbyte/issues/52077)] So, based on the available docs and issues: - Airbyte Cloud currently
does not provide a documented way to see the full HTTP requests for your custom API connection. - Your best option within the product is to inspect the
sync logs for errors and context, and use the
Connection Timeline / Status to jump to the relevant jobs. [[Browsing logs](
https://docs.airbyte.com/platform/operator-guides/browsing-output-logs); [Connection timeline](
https://docs.airbyte.com/platform/cloud/managing-airbyte-cloud/review-connection-timeline)] If you need full request visibility for debugging a custom API connector, the knowledge sources don’t show an official solution today; the feature is only requested, not documented as implemented.