https://api.vimeo.com), using a personal access token. Configview sends only GET requests. It never uploads, edits, moves or deletes anything in Vimeo.
You will end up with 1 required secret (VIMEO_ACCESS_TOKEN) in Configview when setup is complete.
Scope of this integration today. Configview answers “which of our videos can anyone watch, embed anywhere or download?”: every video with its title, owner, folder, status and privacy settings (who can view, where it can be embedded, whether it can be downloaded, who can comment), folders, showcases with their privacy and download settings, and the account plan with storage used. It covers the library of the account that created the token only. It does not read video files, links, descriptions, transcripts, thumbnails, comment text or viewer analytics.
Not covered: people and access. Vimeo’s public API has no endpoint that lists team members, their roles or pending invites, no list of API apps or tokens, and no audit log. Vimeo Enterprise offers SCIM for user provisioning, but it uses a separate tenant-specific address and token and is not part of this integration. To see who has access to Vimeo, use the Vimeo team page or your identity provider.
What you need
- A Vimeo account that owns the videos you want covered (for a team, sign in as the team owner)
- Access to developer.vimeo.com/apps to create an app and generate a token
Step 1: Open the Vimeo page in Configview
Open Configview in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/vimeo
Step 2: Create the access token
- Go to developer.vimeo.com/apps and choose Create an app (any name, for example “Configview read-only”)
- Open the app, then Generate an access token
- Choose Authenticated and tick only the Public and Private scopes. Do not tick Edit, Upload, Delete, Interact, Purchased, Stats or Video Files. Configview needs read access to your own videos and folders and nothing else.
- Copy the token. Personal access tokens do not expire, so rotate it when the person who created it leaves
- In the Configview tab paste it into
VIMEO_ACCESS_TOKENunder Credentials and save
Step 3: Connect and verify
- Click Connect. Configview creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the secret, calls your account (
/me) and fetches one page of videos.
- 401. The token is wrong or was revoked.
- 403. The token is missing the Public or Private scope.
- 429. The app’s call budget for the 15 minute window is spent; Configview waits and retries.
Data Tables
Each table has arun_at column and keeps only the newest run.
Things worth knowing
What the privacy values mean.privacy_view is anybody (public), unlisted (anyone with the link), password, nobody (private to you), users or contacts, or disable (hidden from Vimeo, usually embed only). privacy_embed is public (any site), whitelist (only listed domains) or private. The headline finding is a video that is anybody with privacy_download on.
Passwords are never read. Only the fact that a video or showcase is password protected is recorded.
Embed domain lists are not collected. Vimeo returns the allowed domains of a video one video at a time, which would exhaust the app’s call budget on a large library. Videos with privacy_embed = whitelist are the ones that carry such a list.
Only the token owner’s library. /me is the account that generated the token. Videos that live in another team member’s library, or in a team owner’s library when you use a member’s token, are not listed. Generate the token as the owner of the library you want covered.
Rate limit. Vimeo allows 250 API calls per 15 minutes per app on a free account and 1,000 on a paid one (higher on request), and answers HTTP 429 when exceeded. Configview paces itself at 12 requests a minute and waits for the reset when told to. A library of 5,000 videos is 50 requests (100 videos per page).
Known gaps
- No team members, roles, invites, API apps or audit log: Vimeo does not expose them through its API
- SCIM (Enterprise) is not read
- Per-video embed domain lists are not collected
- Live events, On Demand pages, channels and groups are not collected
What isn’t collected
- Video files, download or play links, thumbnails and embed code
- Video and showcase descriptions, tags, transcripts and captions
- Comment text and any viewer or play analytics
- Video and showcase passwords
- Payment, purchase and subscriber data