Submit once.
Recover the same job.
A lost HTTP response should leave you with a recovery path. Prepare your request before sending it, keep the receipt, and use the same job while you wait.
This page prepares text locally. It does not ask for a key, sign in, send API requests or generate a video. The commands are examples for you to run separately.
- 1. SaveRequest ID + exact JSON
- 2. SubmitOne first request
- 3. RecoverLook up that request
- 4. ReviewReady file + full playback
Already using n8n? Check your format before running a paid step.
Using Postman? Download the two read-only portrait checks.
Using GitHub Actions? See the passing and blocked hosted runs.
Using a private image reference? Check your PNG before uploading.
Prepare a small video pilot
Define what a usable result must show before trying it. The proposed paper-boat test below is a simple geometry, water-contact and camera-motion exercise; this particular request has not been generated.
Watch the wheel-contact test and copy the eight-second prompt
Two animated examples show the difference between a wheel stopping with a gap and a wheel touching its stop. The sound marks the contact frame. This nine-second illustration was built locally as a review guide.
Copy this proposed scene into the prompt field
Vertical 9:16, eight seconds, one continuous waist-low tracking shot. At 0–1 s a scuffed wheeled hard case rolls out of a service elevator. At 1–4 s an adult courier runs alongside it and gets ahead, holding a rubber doorstop. At 4–6 s the courier sets the wedge in the front wheel’s path. Keep the wheel and wedge visible as the case bumps to a stop. At 6–8 s the courier steadies the handle. End on the case still, just short of a painted floor line. Wheels rumble, one rubber thud at contact, no dialogue or music.
For this proposed pilot, select the eight-second Veo 3.1 recipe and Portrait. Check the exact format and live admission below before choosing funding. On playback, check the first second, the wheel’s contact with the wedge, and the timing of the thud.
Add one to three IDs, one per line in the order you want to use them. Get these IDs by uploading private PNGs through the API. Use an owned or permitted image of an object, setting or clothing without people or faces. The planner keeps the IDs in this page and your downloaded JSON.
Check your PNG locally before requesting a reference ID.
Try a picture of your own folded paper boat. Ask for a slow push toward the bow while the folds and colour stay visible. Ingredient images guide what appears in the scene. For timed start and end frames, check that separate recipe.
Check the live model catalog and credit price. Find veo31-ingredients-8s-720.
30-second request · 1 credit if paid · 16:9 · requested 1280×720
Before submitting or buying credits: Review the live quote and formats (new tab). Confirm that the selected orientation and size are listed. If capacity or the exact format cannot be verified, wait before starting a new request. Keep any existing job’s request ID and settings unchanged.
Open the raw availability JSON (new tab). Check generation_status and available_formats before submitting.
The quarter-credit Veo 3.1 option allocates about $0.25 from the $99 upfront 100-credit pack, or about $0.63 from one $2.50 credit. The Veo options require paid funding. Output dimensions, delivery and creative quality can vary.
Budget a 30-second edit from eight-second requests
In this example, six charged requests at 0.25 credits use 1.5 credits. Keep five shots and trim each to six seconds for a 30-second edit. On the two-credit pack, the upfront purchase is $5, the requests use $3.75 worth of credits, and 0.5 credits remain.
Open the filled-in budget worksheet or read the shot-planning walkthrough. Replace the example with your own accepted footage and current quote.
This free builder prepares JSON only after you choose. Trial mode never falls back to paid funding. Paid mode can use your credits or balance when you run the command separately.
For these command examples, use 1–80 letters, digits, underscores or hyphens. Choose an ID unused in your account for a new pilot. Keep it with the exact JSON.Your choice sets free_trial explicitly: true for a trial or false for paid funding. Trials require both live availability and account eligibility. This pilot sets auto_retry: false; review retry terms before your first submission.
The JSON you will save
Edits update the preview. Save your chosen version before submitting. If you change the model, prompt or settings for another attempt, use a new ID and keep both records. Changing this local preview does not change a previously submitted job.
Check a private reference PNG
Use this before uploading an image through the SeedanceCheap API. Your image stays in this browser.
Use a still, non-interlaced 8-bit RGB or RGBA PNG, at most 2 MiB. Each side must be 300 to 2,048 pixels.
Choose a file to see its result.
After the local check, follow the private reference upload steps. The API checks the file again and returns the reference ID for your recipe.
Check a portrait video format in Postman
Download the Postman collection JSON and import the file into your own workspace. Send the text or image-reference GET that matches your scene.
Look for HTTP 200, a fresh observation, and the exact 9:16 and 720x1280 values in the same format row. All three tests must pass before moving on to the live quote and your funding review.
The checks use no API key, private image IDs or credits. They create no job and reserve no capacity. Each request has a link to its own live quote.
Check your planned format in n8n
A ratio and size can each look valid and still be wrong together. Run this free, read-only workflow before adding a generation step.
- In a new n8n workflow, choose Import from URL and paste the address of the tested workflow JSON. You can also save it as
workflow.jsonand choose Import from File. - In Choose recipe and format, set the exact
model,ratioandsizeyou plan to use. Leave your prompt, API key and account details out of the workflow. - Run it manually and inspect Review or wait.
REVIEW_FUNDINGmeans the current catalog lists the pair. Review the live price and your funding separately.WAIT_FORMATmeans the pair is missing.
Try veo31-text-8s-720 with 9:16 and 720x1280. Then change only the ratio to 16:9. When both original format rows are available, the first run passes the format check and the second returns WAIT_FORMAT.
Each run reads the public catalog once. It makes no generation or purchase request and does not reserve capacity. Read all workflow decisions and inspect the source.
Check a video format in GitHub Actions
Inspect both hosted runs for the same eight-second Veo 3.1 text recipe. They read the public catalog before a separate funding review.
- Passing portrait check ·
9:16with720x1280returnedREVIEW_FUNDING. - Blocked mismatch check · changing only the ratio to
16:9returnedWAIT_FORMAT.
Copy the pinned workflow example to call it from your own repository. The manual runs used no API key, account details or generation credits.
Check the current portrait quote before choosing funding. The run results are point-in-time checks.
Use the saved request from your terminal
Use your studio API key in the server environment variable SEEDANCECHEAP_API_KEY. Keep the downloaded JSON in your working folder. No credential belongs in this page.
Check live admission
Run this read-only GET before choosing funding. It uses no API key. Before starting a new job, check that generation_status is available and available_formats includes the exact ratio and size from the saved JSON. Check your account funding separately.
Check a saved JSON file against the public catalog with a local Python example. Your saved prompt stays on your device.
Open API access when you’re ready
Sign in or create an account, then open API access in the same workspace. The account page opens in a new tab so you can keep this draft open.
1. Submit the saved JSON
Save the response and its job ID. A connection failure alone does not tell you whether the server accepted the request.
2. Recover a response you missed
Look up the saved request first. If replay is needed, send that same ID and unchanged JSON; the documented replay returns the original job.
Run the offline recovery cases to see how a lost create response, a failed lookup and a ready job lead to different next steps.
3. Check that job
Replace vid_YOUR_ID with the ID returned by create or recovery. Space status checks, for example 30 seconds apart, and keep your application’s waiting screen tied to this job.
4. Download after Ready
Download within 48 hours after delivery, before the exact expiry time shown in your studio or job receipt. Check the curl exit code before opening the file. Use the local MP4 checker to decode it and compare its encoded size with your request. Play the full result to judge motion and sound. Check whether a later trim dropped audio.
The JSON commands require curl 7.76 or newer for --fail-with-body. HTTP errors return a nonzero exit code; their saved JSON is an error receipt, not a successful job. Windows examples use curl.exe.
Make the next decision from the receipt
| What you see | Next step |
|---|---|
| Active, uncertain or waiting for a service retry | Keep the same job ID and check its status before submitting another request. |
| 403 on the trial | Stop and review whether trials are enabled and your account is eligible. Trial mode does not fall back to paid generation. |
| 409 conflict | Compare your saved JSON. Reusing an ID with changed inputs is not a new pilot. |
| 429 or 503 | Read the response, wait, and check the existing request before retrying. |
| Confirmed failed | Check that the original charge was restored before deciding on a new attempt. What to check next. |
| Ready | Save the MP4 and review it against your checks before using or publishing it. |
After a confirmed failure
Look up the same job ID and check its status and any retry notice. For a confirmed failed request, the original reserved charge is restored. Check your workspace credits or balance. If the status or restoration is unclear, give support the job ID and the error shown. Keep your API key private.
Once the job is final and the charge is restored, check the exact recipe, format and live quote again. If you choose another paid attempt, save it under a new request ID. Replaying the old ID with unchanged input retrieves the original job. See the live status and restoration rules.
Service timing and available formats can change. The live documentation and your actual receipt take precedence over this example. Check current one-time pack totals on the pricing guide. The credit totals above describe fixed request recipes and are subject to current admission. Review your selected funding route in the saved JSON.
Count paid attempts and approved seconds with the free calculator →
New to prompts? Plan your first scene →