Explore/Seedance 2.5
Video

Seedance 2.5

Finalize a completed Seedance 2.5 draft at 1080p using its request_id.

View docs
import { config, higgsfield } from "@higgsfield/client/v2";config({  credentials: process.env.HF_CREDENTIALS,});const result = await higgsfield.subscribe(  "bytedance/seedance-2.5/finalize-draft",  {    input: {      "draft_id": "string",      "resolution": "1080p"    },    withPolling: true,  },);console.log(result);

Seedance 2.5 Finalize Draft turns a completed Seedance 2.5 draft into a 1080p video. Use model ID bytedance/seedance-2.5/finalize-draft after generating and reviewing a draft.

Authentication

Send Authorization: Key KEY_ID:KEY_SECRET on every request. The cURL examples use $HF_KEY:

export HF_KEY="YOUR_KEY_ID:YOUR_KEY_SECRET"

Keep these credentials on the server; do not expose them in browser code.

Finalization parameters

POST https://api.higgsfield.ai/bytedance/seedance-2.5/finalize-draft with a JSON body:

ParameterTypeRequiredDefaultDescription
draft_idstring (UUID)Yes—Public request_id of a completed draft owned by your account.
resolutionstringNo"1080p"Only 1080p is supported.

Draft-to-final workflow

The example below starts with a text-to-video draft. The same finalization endpoint works with all five supported generation endpoints.

1. Create a draft

Send the usual inputs for your generation endpoint with draft: true. Omitting draft or setting it to false keeps regular generation behavior. Draft mode forces 480p, MP4, and standard bitrate, even if the request selects another supported resolution, format, or bitrate.

curl --request POST \ --url 'https://api.higgsfield.ai/bytedance/seedance-2.5/text-to-video' \ --header "Authorization: Key $HF_KEY" \ --header "Content-Type: application/json" \ --data @- <<'JSON' { "prompt": "A cinematic scene at sunset", "duration": 5, "draft": true } JSON

Save the request_id from the POST response. This is the public request ID (JobSet ID) that you will pass as draft_id; do not use a video URL, an internal job ID, or a provider task ID.

2. Wait for the draft and review it

Poll the returned status_url with the same authorization header, or use the status endpoint directly:

DRAFT_REQUEST_ID="REPLACE_WITH_DRAFT_REQUEST_ID" curl --request GET \ --url "https://api.higgsfield.ai/requests/${DRAFT_REQUEST_ID}/status" \ --header "Authorization: Key $HF_KEY"

Wait until status is completed, then review the preview at video.url in the status response. Do not finalize a request that is queued, in progress, failed, canceled, or blocked by moderation.

3. Finalize at 1080p

Submit a new request to bytedance/seedance-2.5/finalize-draft. Replace the example UUID below with the draft's saved request_id:

curl --request POST \ --url 'https://api.higgsfield.ai/bytedance/seedance-2.5/finalize-draft' \ --header "Authorization: Key $HF_KEY" \ --header "Content-Type: application/json" \ --data @- <<'JSON' { "draft_id": "00000000-0000-4000-8000-000000000001", "resolution": "1080p" } JSON

The response contains a new request_id and status_url for finalization. Poll that new status URL until status is completed; its video.url is the final video. Keep the draft and finalization request IDs separate.

Pricing

Draft generation and finalization are separate paid requests. Each is billed per output second at its own resolution. Finalization uses the duration and video-input pricing tier saved with the draft and applies the 1080p rate; it does not reuse the draft's charge. The draft charge is not deducted from the finalization charge.

Input type480p draft, USD / output second1080p finalization, USD / output second
Without video input (text, images, or audio only)$0.1177$0.6518
With video input$0.1387$0.7858

These are standard self-serve rates. Total cost for a draft followed by one finalization is output seconds × (draft rate + finalization rate). If you stop after viewing the draft, only the draft request is charged. Input-video seconds are not added to the billing multiplier. For video edit, output duration is derived from the primary input video; for video extend, the billed duration is the requested extension.

Requirements and limits

  • Use a completed draft created with draft: true on one of the five bytedance/seedance-2.5/ generation endpoints listed below. A regular generation cannot be finalized as a draft.
  • The draft must belong to the same account as the finalization request and contain a single video job.
  • Finalize within seven days of draft creation and before the request's retention expires. A shorter account retention or Hf-Expires-After setting can shorten this window. If the status response includes expires_at, respect that timestamp as well as the seven-day limit. Deleted or purged drafts cannot be finalized.
  • Only 1080p is supported for finalization. It is also the default when resolution is omitted.
  • Finalization accepts draft_id and resolution. Prompt, media inputs, audio settings, aspect ratio, and duration come from the original draft. To change those inputs, create a new draft.
  • Draft creation and finalization use TTUS. You do not need to select a provider or send a provider task ID.

Supported draft endpoints

  • bytedance/seedance-2.5/text-to-video
  • bytedance/seedance-2.5/image-to-video
  • bytedance/seedance-2.5/reference-to-video
  • bytedance/seedance-2.5/video-edit
  • bytedance/seedance-2.5/video-extend