Vimeo connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Vimeo from the Previews page. See Manage Databricks previews.
The managed Vimeo connector in Lakeflow Connect requires a paid Team or Enterprise plan, authenticates with a personal access token, and ingests four tables. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Vimeo plans does the connector require?
Team, team member, and team role data require a paid Team or Enterprise plan. The audit_logs table requires an Enterprise account with audit logs enabled, and a personal access token generated by an Account Owner or Administrator from an API app created on that Enterprise account. See Configure authentication to Vimeo.
Which tables does the connector support?
The connector supports teams, team_members, team_roles, and audit_logs. For the destination schemas, see Destination table schemas.
How far back can the connector ingest data?
For the incremental audit_logs table, the first sync ingests events from the previous 364 days, and each later sync ingests events created after the last run. To ingest less history, set a later start date with the start_datetime option. The connector clamps earlier dates to 364 days back, just under Vimeo's 365-day limit on audit log ranges. The teams, team_members, and team_roles tables are full refresh, so each run reingests all available records.
Which authentication methods does the connector support?
The connector supports a Vimeo personal access token (bearer token) only. OAuth U2M, OAuth M2M, and basic authentication with a username and password aren't supported.