Skip to content

Connect Vimeo Pro/Business with OAuth and API credentials.

Integrations (Vimeo OAuth)

Location: MediaBlaster → General Settings → Integrations tab

Use this tab to connect your Vimeo Pro or Business account so MediaBlaster can fetch video metadata, HLS stream URLs, thumbnails, tags, and descriptions.

Before you begin

  1. Enable Enable Vimeo Integration on MediaBlaster → General Settings and save.
  2. Log in to Vimeo Developer and create an app (or open an existing one).
  3. Note your app's Client ID and Client Secret.
  4. You will need to add a Redirect URI from MediaBlaster into your Vimeo app settings.

Step-by-step connection

  1. Open MediaBlaster → General Settings and click the Integrations tab.
  2. Copy the Redirect URI displayed on the page.
  3. In your Vimeo app settings, add that URI to Redirect URIs and save.
  4. Paste the Client ID and Client Secret into MediaBlaster and save settings.
  5. Click Connect Vimeo and approve access on Vimeo's authorization screen.
  6. Return to WordPress — the Client Token is saved automatically (you do not need to paste it manually).

After connecting

  • Use the Vimeo URL field on video posts and click Load Video Data to import a single video.
  • Use MediaBlaster → Vimeo Mass Import for bulk imports (card grid, Ready to Import default, Review & Import). See Vimeo Mass Import.
  • Configure title/description import behavior under the Vimeo Settings tab.

Troubleshooting

ProblemWhat to try
OAuth redirect failsConfirm the Redirect URI in Vimeo matches exactly (including trailing slash if shown).
SSL certificate errorsCommon on local dev environments. MediaBlaster prefers WordPress's CA bundle; check PHP/cURL on your host.
Token missing after connectRe-save Client ID/Secret, then click Connect Vimeo again.
Existing token from older installsPreviously saved tokens under rovidx_smart_tv_api_options continue to work without re-authorizing.

Security

Only site administrators (manage_options) can view or change integration credentials. Client Secret fields use password-style inputs. Do not share API credentials publicly.

Was this helpful?