Skip to content

Integrations

Everything it connects to, and exactly what it asks for.

VidForge AI has no public API of its own — it is a desktop application, not a service. What it does have is a documented set of integrations, each using your own credentials. This page is the reference.

Looking for a REST API to drive VidForge AI remotely?

There isn't one yet. For automation today, the practical hook is the Publishing Center's folder watcher: drop a rendered video into a watched folder and the queue picks it up, which makes the app composable with whatever generates or schedules your files. If a local control API would help your workflow, tell us at support@vidforgeai.online.

Publishing platforms

Scopes, fields and delivery behaviour.

Listed as the software actually implements them. Where a platform delivers uploads as drafts rather than posts, it says so.

YouTube

Available in v2.2.1

YouTube Data API v3

Uploads a rendered video to a channel you own, and reads the channel name and avatar so you can tell connected accounts apart.

How a video arrives

Uploaded straight to your channel with the visibility you choose.

Scopes requested

  • https://www.googleapis.com/auth/youtube.upload
  • https://www.googleapis.com/auth/youtube.readonly
  • https://www.googleapis.com/auth/userinfo.email

Profile fields read

  • Channel ID
  • Channel title
  • Avatar URL
  • Email address

Used only to label the connected account in the interface.

TikTok

Available in v2.2.1

TikTok Content Posting API (v2)

Sends a rendered video to your TikTok inbox as a draft, and reads your display name and avatar so you can tell connected accounts apart.

How a video arrives

Delivered to your TikTok inbox as a draft. You review it inside the TikTok app and post it yourself — VidForge AI never posts publicly on your behalf.

Scopes requested

  • video.upload
  • user.info.basic

Profile fields read

  • Open ID
  • Display name
  • Avatar URL

Used only to label the connected account in the interface.

Facebook

Available in v2.2.1

Facebook Graph API

Publishes a rendered video to a Facebook Page you manage, and lists your Pages so you can pick the destination.

How a video arrives

Published to the Facebook Page you select.

Scopes requested

  • pages_show_list
  • pages_manage_posts
  • pages_read_engagement

Profile fields read

  • Page ID
  • Page name
  • Page avatar

Used only to label the connected account in the interface.

Instagram

In development

Instagram Graph API (planned)

Planned. Instagram Reels publishing through the Instagram Graph API is in development and is not part of v2.2.1.

How a video arrives

Not yet available.

No permissions are requested from this platform in v2.2.1, and no integration is present in the installed application.

X

In development

X API v2 (planned)

Planned. Video posting to X is in development and is not part of v2.2.1.

How a video arrives

Not yet available.

No permissions are requested from this platform in v2.2.1, and no integration is present in the installed application.

OAuth

How authorisation works.

The installed-application flow, with the redirect landing on your own computer rather than on a server of ours.

  1. Register a developer application

    Create your own app in Google Cloud Console, the TikTok for Developers portal or Meta for Developers. Choose the installed or desktop application type where the console offers one.

  2. Register the loopback redirect URI

    The app receives the OAuth redirect on http://127.0.0.1:8734 by default. Google's desktop client type accepts any loopback port automatically; TikTok and Meta require the exact port to be registered, so add the one shown in Settings.

  3. Paste the client ID and secret into Settings

    These stay in your local configuration file. Nothing is transmitted to us, and no credentials of ours ship inside the installer.

  4. Authorise each account

    The app opens the platform's own consent screen in your browser. You approve there, the redirect returns to your own machine, and the token is encrypted to local storage.

Tokens are encrypted at rest with Fernet using a key generated on first run and stored only on your machine, and refreshed in the background before expiry. Revoking access at the platform invalidates them immediately regardless of what is stored locally — see the data deletion page for where each platform's revocation screen lives.

AI and media providers

Bring the keys you already have.

Every provider is optional except on-device transcription. A service receives nothing unless you supply a key and enable the feature that uses it.

Cloud providers

Your key, your account

  • OpenAI

    Privacy

    Script writing, research, storyboard and scene planning; optional text-to-speech.

  • Anthropic

    Privacy

    Script writing, research and SEO metadata generation (default text provider).

  • ElevenLabs

    Privacy

    Cloud voice generation.

  • Pexels

    Privacy

    Stock video and image search.

  • Pixabay

    Privacy

    Fallback stock video and image search.

  • Google / YouTube

    Privacy

    Publishing to a YouTube channel you own.

  • TikTok

    Privacy

    Delivering a video draft to your TikTok inbox.

  • Meta / Facebook

    Privacy

    Publishing to a Facebook Page you manage.

Runs on your device

Nothing leaves

  • VoxCPM2

    Local voice generation and voice cloning.

  • Kokoro

    Local, lightweight voice generation.

  • OpenAI Whisper

    Subtitle transcription and word-level timing.

Choosing a local voice model means your script text never leaves your computer for narration, and subtitle transcription is always local regardless of configuration.

Connect one account and watch what it asks for.

The consent screen is the platform's own. Read the permissions there and compare them to this page.

Download for WindowsRead the privacy policy