Authentication Methods

HeyGen offers multiple integration paths—Direct API, MCP, and Skills—each with its own authentication method. Understanding which flow applies to your use case will determine how you authenticate and how usage is billed.

Integration Path	Auth Method	Billing Source
MCP (Model Context Protocol)	OAuth	Web plan + premium credits
Skills	API Key	API balance (API dashboard)
Direct API	API Key	API balance (API dashboard)

📘
Note:

For usage quotas, request limits, and pricing details, see Limits page.

OAuth Authentication (MCP)

When you access HeyGen features through MCP — for example, HeyGen tools embedded within an MCP-enabled host like Claude — the connection uses an OAuth authentication flow. In this flow, users authorize access through a standard consent screen rather than managing API keys directly.

Requirements:

An active HeyGen web plan (not just an API-only account)
Premium credits available on your web plan

Usage is deducted from your web plan's premium credit balance, not from any separate API balance.

API Key Authentication (Skills & Direct API)

When you integrate with HeyGen through Skills or call the API directly, authentication uses an API key passed via the X-Api-Key header.

Requirements:

A HeyGen API key (generated from Settings → API in your HeyGen dashboard)
Sufficient API balance in your API dashboard

Usage is deducted from your API dashboard balance, which is separate from any web plan credits.

Choosing the Right Path

MCP is ideal if you're working within an MCP-compatible environment and prefer OAuth-based access without managing keys. You'll need a web plan with premium credits.
Skills or Direct API is the right choice if you're building custom integrations, automating workflows, or need programmatic control. You'll manage an API key and fund your API dashboard balance separately.

Important: The two billing pools — web plan premium credits (OAuth/MCP) and API dashboard balance (API Key) — are independent. Credits in one do not apply to the other.