Googleapis Bigquerydatatransfer

Connector for the googleapis-bigquerydatatransfer API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://bigquerydatatransfer.googleapis.com
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• bigquerydatatransfer_projects_transferconfigs_ru — GET /v1/{name} — Returns information about the particular transfer run.
• bigquerydatatransfer_projects_locations_list — GET /v1/{name}/locations — Lists information about the supported locations for this service.
• bigquerydatatransfer_projects_locations_datasour — GET /v1/{parent}/dataSources — Lists supported data sources and returns their settings.
• bigquerydatatransfer_projects_transferconfigs_li — GET /v1/{parent}/transferConfigs — Returns information about all transfer configs owned by a project in the specifi
• bigquerydatatransfer_projects_transferconfigs_pa — PATCH /v1/{name} — Updates a data transfer configuration. All fields must be set, even if they are
• bigquerydatatransfer_projects_locations_enrollda — POST /v1/{name}:enrollDataSources — Enroll data sources in a user project. This allows users to create transfer conf

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: bigquerydatatransfer_projects_transferconfigs_ru
# (attach an 'oauth' credential to the task — no inline secrets)