Docs · v1

Authentication

Every Platform API request requires a key from Settings → API Integration. Send it as a request header. Keys are tied to an active subscription with API access.

Request header

Parameters

Header	Required	Description
`X-Api-Key`	Yes	Platform API key for the authenticated MakeUGC account

Header bash

X-Api-Key: YOUR_API_KEY

Authenticated request

Call any v1 route with the header. This example lists avatars:

cURL bash

curl -X GET "https://app.makeugc.ai/api/platform/video/avatars" \
  -H "X-Api-Key: YOUR_API_KEY"

JavaScript javascript

const response = await fetch("https://app.makeugc.ai/api/platform/video/avatars", {
  headers: {
    "X-Api-Key": process.env.MAKEUGC_API_KEY,
  },
});

if (response.status === 401) {
  throw new Error("Not authenticated");
}

Python python

import os
import requests

response = requests.get(
    "https://app.makeugc.ai/api/platform/video/avatars",
    headers={"X-Api-Key": os.environ["MAKEUGC_API_KEY"]},
)
response.raise_for_status()

Status codes

200 — authenticated request succeeded
401 — missing, invalid, or unauthorized API key

401 response

JSON json

{
  "status": false,
  "message": "Not authenticated"
}

See error codes for the full status table and rate limits for credit usage after a successful call.

Questions

How do I authenticate with the MakeUGC API?

Send your Platform API key on every request in the X-Api-Key header. Create the key in Settings → API Integration. Do not put the key in query strings or client-side frontend code.

What happens if authentication fails?

The API returns HTTP 401 Not authenticated. Check that the header name is X-Api-Key, the key is active, and the account has an active subscription with API access.

Can I use a Bearer token instead of X-Api-Key?

No. The Platform API authenticates with the X-Api-Key request header only. Claude MCP connectors accept the same key as X-API-Key when registering the remote server.