Authentication
How to authenticate your requests and select the workspace
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.
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:
curl https://api.cut.pro/api/v1/workspace \
-H "X-Api-Key: $CUTPRO_API_KEY"curl https://api.cut.pro/api/v1/workspace \
-H "Authorization: Bearer $CUTPRO_API_KEY"The rate limit is per key, and every response carries what is left of it in the X-RateLimit-Remaining and X-RateLimit-Reset headers. See Errors and limits.
A missing, revoked or invalid key comes back like this:
{ "code": "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.
Every request operates on that workspace automatically. No extra header is needed.
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 connection_id 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.