Authentication

Every API request needs an API key.

Generating your key

Go to API keys in your account settings and click New key. Store the key somewhere safe: it is not shown again after it is created.

Caution

The key grants access to the credits and the connected accounts of the workspace. Keep it on your server, in an environment variable, never in browser or app code.

Sending the key

Send the key in every request, in one of two ways:

Header X-Api-Key

curl https://api.cut.pro/api/v1/workspace \
  -H "X-Api-Key: $CUTPRO_API_KEY"

Authorization Bearer

curl https://api.cut.pro/api/v1/workspace \
  -H "Authorization: Bearer $CUTPRO_API_KEY"

A missing, revoked or invalid key comes back like this:

Response 401

{ "code": "UNAUTHORIZED", "message": "Unauthorized" }

Workspaces

An API key is bound to one or more workspaces (scoped tokens, Cloudflare style). Credits, submissions, clips, and renders always belong to the workspace the request resolves to.

Single-workspace key

Every request operates on that workspace automatically. No extra header is needed.

Multi-workspace key

Send the X-Workspace-Id header on each request to choose which workspace the call hits:

curl https://api.cut.pro/api/v1/balance \
  -H "X-Api-Key: $CUTPRO_API_KEY" \
  -H "X-Workspace-Id: 7401220118845503"

Without the header, the response is 400 MISSING_WORKSPACE_ID, including the list of allowed workspaces.

Tip

Call GET /workspace to inspect which workspace the current request resolved to, along with the plan and your role in it.

Social connections

Connected social accounts (TikTok, Instagram, YouTube, etc.) are the IDs you pass as connectionId when creating a post. The lifecycle of connections is not exposed by the API. To connect a new account, go to cut.pro and use the OAuth flow inside the app.