Skip to main content
Permission scopes let you restrict an API key to the HeyGen resources and actions it needs. Each scope uses the form resource:read or resource:write.

How permissions work

  • An endpoint can require one scope or several scopes. When several are listed, the key must satisfy all of them.
  • A resource:write grant also satisfies resource:read for the same resource. A read grant never satisfies a write requirement.
  • Full-access keys use *:*. Read-only keys use *:read, which satisfies every current and future read requirement.
  • A key without the required permissions receives a 403 insufficient_api_key_scope response.
Create and manage keys in the HeyGen API dashboard.

Scope-to-endpoint mapping

This reference is generated from the permission metadata in the published OpenAPI specification. Only public, documented endpoints are included. An endpoint with multiple requirements appears under every required scope.

account:read

ai_clipping:read

ai_clipping:write

assets:read

assets:write

avatars:read

avatars:write

brand:read

brand:write

filler_removal:read

filler_removal:write

hyperframes:read

hyperframes:write

lipsync:read

lipsync:write

templates:read

translations:read

translations:write

video_agent:read

video_agent:write

videos:read

videos:write

voices:read

voices:write

webhooks:read

webhooks:write