# White-label

> Offer clipping, rendering and posting under your own brand: one workspace per client and a link for them to connect their own accounts, with no Cut.Pro account.

The [terms of service](https://cut.pro/terms) allow reselling the API, white-labeling it and building your own product on it, under your brand and at your price, with no separate contract. This page walks through the flow: each client gets a workspace, connects their accounts through a link, and you run everything through the API.

## 1. Create a workspace per client

A workspace keeps each client's videos, clips, renders, connected accounts and posts apart.

```bash
curl -X POST https://api.cut.pro/api/v1/workspaces \
  -H "X-Api-Key: $CUTPRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Central Bakery" }'
```

```json title="201 Created"
{ "id": "7412990011220001", "name": "Central Bakery", "is_personal": false, "created_at": "2026-11-20T15:00:00.000Z" }
```

The key that created it already reaches the new workspace. Store the `id` next to the client in your system and send it as `X-Workspace-Id` on every call for that client:

```bash
curl https://api.cut.pro/api/v1/connections \
  -H "X-Api-Key: $CUTPRO_API_KEY" \
  -H "X-Workspace-Id: 7412990011220001"
```

Without the header, requests keep landing where they did before you created workspaces, so nothing that already works changes. `GET /workspaces` lists them all and `PATCH /workspaces/{id}` renames one.

> Credits and plan belong to each workspace. A new workspace starts on the free plan with no credits.

## 2. Ask for the connect link

```bash
curl -X POST https://api.cut.pro/api/v1/connections/link \
  -H "X-Api-Key: $CUTPRO_API_KEY" \
  -H "X-Workspace-Id: 7412990011220001" \
  -H "Content-Type: application/json" \
  -d '{
    "platform": "instagram",
    "return_url": "https://app.yourbrand.com/clients/42/accounts",
    "state": "client-42"
  }'
```

```json title="200 OK"
{ "url": "https://api.cut.pro/api/v1/connections/start?link=…", "expires_at": "2026-11-21T15:00:00.000Z" }
```

Hand the `url` to your client: behind a button in your dashboard, by email or by message. They open it, sign in to the network and authorize. Nobody needs a Cut.Pro account.

| Field | What it does |
|---|---|
| `platform` | `youtube`, `tiktok`, `instagram`, `facebook`, `threads`, `linkedin`, `pinterest`, `bluesky`, `twitch`, `kick` or `discord`. |
| `return_url` | Where the person goes when done. `https`, or `http` on `localhost` while you test. Without it, they land on Cut.Pro. |
| `state` | Any text of yours, up to 512 characters, returned untouched. Use it to know which client the answer belongs to. |
| `connection_id` | Reconnects an account whose access was revoked, keeping its `id` and scheduled posts. |

A link works once and expires in 24 hours. If the person cancels or the sign-in fails, the same link works again. While a sign-in is in progress, a second tab gets `LINK_IN_USE`.

## 3. Handle the return

When the person is done, the browser goes to `return_url` with:

| Parameter | Value |
|---|---|
| `status` | `connected` or `error`. |
| `platform` | The link's network. |
| `connection_ids` | The `id` of each connected account, comma separated. More than one when a Facebook sign-in grants several Pages. |
| `warning` | `FACEBOOK_PAGES_PARTIAL` when some Pages did not fit the limit. |
| `code` | On `error`, the reason, such as `LINK_EXPIRED`, `LINK_USED`, `CONNECTION_LIMIT_REACHED` or the error the network returned. |
| `state` | Your `state`, as sent. |

```text
https://app.yourbrand.com/clients/42/accounts?status=connected&platform=instagram&connection_ids=7412990011229001&state=client-42
```

The return travels through the person's browser. Before saving the connection in your system, confirm it with `GET /connections/{id}` in the client's workspace instead of trusting the URL alone.

> The connection happens with no Cut.Pro screen in between. That is why Facebook connects every Page the person authorized, LinkedIn connects the profile and Tumblr the primary blog, up to the plan's account limit.

## 4. Work as usual

With the client's `X-Workspace-Id`, the rest of the API works the same: [clip](https://cut.pro/docs/en/clipping), [render](https://cut.pro/docs/en/rendering) and [post](https://cut.pro/docs/en/publishing) to their accounts. To deliver the video from your own domain, download the MP4 and serve it from your storage.

## What still shows

- The Google, TikTok and Meta consent screens show the app name, which is Cut.Pro's. Each network requires an app it has reviewed, so that name does not change per client.
- The connect link goes through `api.cut.pro` for a moment before opening the network's sign-in.

## Errors

| Code | When |
|---|---|
| `WORKSPACE_LIMIT_REACHED` | The account reached the limit of workspaces created through the API. |
| `INVALID_RETURN_URL` | `return_url` is not `https` (nor `http` on `localhost`). |
| `CONNECTION_LIMIT_REACHED` | The workspace already has as many accounts of that network as the plan allows. |
| `PLATFORM_UNAVAILABLE` | The workspace's plan does not include the network, or it is not released yet. |
| `CONNECTION_NOT_FOUND` | The `connection_id` to reconnect is not in this workspace or belongs to another network. |
