Publish to social networks

A post publishes edits to connected accounts. Each edit and account pair becomes an item, with its own state: in a post to TikTok and YouTube, one item can go out and the other fail.

You do not need to render first. The post renders what is missing and publishes.

Choose the accountsCopy Anchor Link

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

Each connection carries id, platform, username and audience numbers. The id is the post's connection_id. If the account the person wants is not in the list, request the connection link and hand it to them:

curl "https://api.cut.pro/api/v1/connections/link?platform=tiktok" \
  -H "X-Api-Key: $CUTPRO_API_KEY"

The connection is made by the account owner, in the browser. When they come back, list again.

Create the postCopy Anchor Link

curl -X POST https://api.cut.pro/api/v1/posts \
  -H "X-Api-Key: $CUTPRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "videos": [
      {
        "edit_id": "7412910087700001",
        "targets": [
          {
            "connection_id": "7390012299881100",
            "metadata": { "tiktok": { "title": "The chorus everyone knows #music", "privacyLevel": "PUBLIC_TO_EVERYONE" } }
          },
          {
            "connection_id": "7390012299881200",
            "metadata": { "youtube": { "title": "The chorus everyone knows", "categoryId": "10", "privacyStatus": "public" } }
          }
        ]
      }
    ],
    "scheduled_at": "2026-10-30T12:00:00.000Z"
  }'

{ "id": "7412930011223344", "item_count": 2, "scheduled_at": "2026-10-30T12:00:00.000Z", "status": "pending" }

• edit_id comes from the clip, the render or a generated video. Several videos in a single post publish several clips at once.
• scheduled_at schedules it, in ISO 8601 in the future. Without it, it publishes now.

Metadata per networkCopy Anchor Link

metadata takes a key with the network's name and, inside it, the network's own fields, with its own names (privacyLevel, categoryId). It is the only part of the API outside snake_case: the content goes to the network as is.

All of them accept coverImageId for the cover. The limits of each field, and the other networks, are in POST /posts. A network that is still on its way rejects the whole request with 400 PLATFORM_UNAVAILABLE, before creating anything.

Follow alongCopy Anchor Link

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

Each item goes through pending → rendering → publishing → completed or failed. On completed, published_url is the video's link on the network. On failed, error_code says the reason.

The post summarizes the items:

Poll every 10 to 30 seconds. An item that failed goes back to the queue with:

curl -X POST https://api.cut.pro/api/v1/posts/7412930011223344/items/7412930011223401/retry \
  -H "X-Api-Key: $CUTPRO_API_KEY"

Change, bring forward or cancelCopy Anchor Link

ErrorsCopy Anchor Link