Connections

Manage Connections — sync pipelines from Sources into your organization's data warehouse.

Verbs: list, get, create, update, delete

Usage

revos connections list [--page-size <n>] [--order-by <field>] [--filter <expr>] [--fields <cols>] [--columns <cols>] [--json]
revos connections get <connection-id> [--json]
revos connections create --body JSON|@file|- [--json]
revos connections update <connection-id> --body JSON|@file|- [--json]
revos connections delete <connection-id> [--json]

Examples

revos connections list --json
revos connections list --page-size 10 --order-by 'createdAt desc'
revos connections get 8f2f4dff-e083-42bd-b562-67f0ec76cd2a
revos connections create --body @./connection.json
revos connections update <connection-id> --body '{"status":"active"}'
revos connections update <connection-id> --body '{"prefix":"renamed_"}'
revos connections delete <connection-id>

Table-name prefix

Each Connection has a prefix that is prepended to every destination table name. It must match ^[a-z0-9_]*$ (lowercase letters, digits, and underscores) and be at most 63 characters. If you omit prefix on create, the API auto-generates one from the source (e.g. postgres_). Pass an empty string on update to clear it.

For declarative, file-based management of Connections (with stream mappers, schedules, and Source references), use revos apply instead.