All Collections
OAuth Setup Guides
Setting Up Vimeo OAuth App
Setting Up Vimeo OAuth App
Tristan avatar
Written by Tristan
Updated over a week ago

Firstly, in order for any assets from Vimeo to be synced to the medialake.ai platform, you will need any paid Vimeo membership. Vimeo does not allow videos to be synced to our platform without the user having a paid membership plan.

Setting up OAuth for Vimeo

Step 1: Creating a New App

  1. Click on "Create New App".

Step 2: Configure your Application

  1. Fill out the "App Name" and "Brief Description". Put "medialake" for the app name and a short description in the "Brief Description" box to help you remember in future what the app is for

  2. Select "No. The only vimeo accounts that will have access to the app are my own." when asked "Will people besides you be able to access your app?"

  3. Agree to the terms and click "Create App"

Step 3: Add a Callback URL

  1. Click on OAuth Redirect Authentication, and then click on "Add URL".

  2. Add a Callback URL in the pop-up window. The Redirect URI must be set to something like the following, which will be your Medialake domain followed subdirectory: https://'YOUR_DOMAIN'/vimeo-redirect

Step 4: Add the scopes

  1. On the app dashboard to the left, click on the "Generate an access token" tab.

  2. Make sure the "Authenticated (you) button is selected. It then gives you a selection of different scopes you can add to the platform.

  3. Make sure the following scopes are selected: Public (default), Private, Purchased, Create, Edit, Delete, Interact, Upload, Promo Codes, Stats, and Video Files.

  4. Click on "Generate" below

Step 5: Gather your Credentials

  1. Now make a note of the "Client Identifier" and "Client Secret" on the app details page. Make a note of these for later as you will need to enter these on the integration settings page on the medialake website. These are displayed at the top of the page and in the "Manage App Secrets" section.

Important Considerations

  • Make sure to follow security best practices, especially when handling client secrets.

  • The permissions and configuration might vary based on the specific service or API you're accessing.

Did this answer your question?