GuidesReference

Authentication

Every request to the VideoGen API must include a bearer credential — an API key or an OAuth 2.1 access token.

The VideoGen API accepts two kinds of bearer credentials: an API key (best when you call the API from your own backend) and an OAuth 2.1 access token (best when your app acts on behalf of other VideoGen users). Both are sent the same way — in the Authorization header — and every endpoint works identically regardless of which you use.

If you’re building an integration that connects to other people’s VideoGen accounts, see Sign in with VideoGen for the OAuth flow. Otherwise, use an API key as described below.

API keys

The VideoGen API uses Bearer token authentication. Include your API key in the Authorization header of every request:

$Authorization: Bearer sk_videogen_live_...

Creating a key

  1. Go to app.videogen.io/api
  2. Click Create API key
  3. Copy the key immediately; it is only displayed once

Keeping your key safe

Your API key is a secret. Do not expose it in client-side code (browsers, mobile apps) or commit it to version control. Use environment variables or a secrets manager instead.

$export VIDEOGEN_API_KEY="sk_videogen_live_..."

Making requests

1import { VideoGen } from "@videogen/sdk";
2
3const client = new VideoGen({
4  apiKey: "sk_videogen_live_...",
5});

Error responses

If your key is missing or invalid, the API returns 401 Unauthorized:

1{
2  "message": "Unauthorized"
3}