GET /videos/generations/:id
Live
Open in ChatGPT
(opens in new tab)Last verified: 2026-09-08Endpoint
GET /videos/generations/:idRead the current state of a video job. The base URL is
https://api.modelrush.ai/v1.Request
Generation ID in the path and the same Bearer key used to submit. Send
Authorization: Bearer $MODELRUSH_API_KEY for authenticated routes and Content-Type: application/json for JSON bodies.Response
id, status (queued, in_progress, completed or failed), model, modelrush_region, video_url on success, error on failure; provider_status when available. This differs from GET /predictions/:id, which uses succeeded and outputs. Preserve returned request or generation identifiers. Generated outputs and their Provider file references are removed from the ModelRush database 24 hours after request completion; download anything you need to keep.
Errors
Invalid inputs return a 4xx response with a structured error. A
403 with adult_attestation_required, portrait_rights_attestation_required, or person_rights_confirmation_required must be resolved by the account user and must never be retried automatically. Retry 429 according to Retry-After; retry 5xx failures only with a bounded backoff policy.Spicy model API references
Open a model page for its request parameters and current prices. The four Wan 3 landing pages include a developer API section below the Playground. Read GET /v1/models for current schemas and key-specific access; GET /api/model-pricing returns public prices without authentication; with a valid Bearer API key, it returns the prices applicable to that account.
| Model and API reference | Model ID | Endpoint |
|---|---|---|
| Wan 3 Spicy | modelrush/wan3-spicy | POST /v1/videos/generations |
| Wan 3 Pro Spicy | modelrush/wan3-pro-spicy | POST /v1/videos/generations |
| Wan 3 Prime Spicy | modelrush/wan3-prime-spicy | POST /v1/videos/generations |
| Wan 3 Prime Pro Spicy | modelrush/wan3-prime-pro-spicy | POST /v1/videos/generations |
| Wan 2.7 I2V Spicy | modelrush/wan2.7-i2v-spicy | POST /v1/videos/generations |
| Wan 2.2 I2V Spicy | modelrush/wan2.2-i2v-spicy | POST /v1/videos/generations |
| Wan Animate Spicy | modelrush/wan-animate | POST /v1/videos/generations |
| FlashVSR Spicy | modelrush/flashvsr | POST /v1/videos/generations |
Video polling via GET /v1/videos/generations/:id ends with completed or failed and returns video_url on success. The unified GET /v1/predictions/:id instead uses succeeded and outputs. Follow the contract of the poll_url you use. Wan 3 reference-video time plus generated time cannot exceed 30 seconds. Only Prime and Prime Pro currently accept prompt_extend; check the per-model schema. LoRA supports three optional weight arrays, 480P/720P and 5/8 seconds. Wan Animate and FlashVSR use the video generation endpoint with source media. FlashVSR duration must equal the input video length rounded to the nearest whole second (minimum 1); otherwise the request fails with video_duration_mismatch (or video_duration_unverified if the video cannot be read) before any charge.
All Spicy models require adult-access confirmation on the account. API keys must permit the selected model and capability. Keep keys server-side and reuse Idempotency-Key for retries where supported. Wan Animate has the additional signed-quote and x-request-id requirements in the video documentation.
Wan Animate: confirm a signed quote before submission
For new modelrush/wan-animate requests, remove duration. The server measures the reference video, which must be longer than 0 and no longer than 30 seconds. The output follows that reference length; 5/8 seconds is not an output-length control. The quote measures the reference and reads the current price without starting a generation or reserving credits. Review billing.maximum_charge_cents (whole cents, rounded up for the task) before submitting. The final customer charge cannot exceed this confirmed maximum; unused reserved credits are released. A quote is valid for 10 minutes. Normal account, media-access and credential requirements still apply.
Public API: POST https://api.modelrush.ai/v1/videos/generations/quote, then POST https://api.modelrush.ai/v1/videos/generations. Use Authorization: Bearer with a server-side API key permitted for this model. Agent runtime: POST https://modelrush.ai/api/agent/v1/videos/generations/quote, then POST https://modelrush.ai/api/agent/v1/videos/generations. Use the Agent credential with media:write and an active Agent run, not a public API key. The quote has no generation charge; it does not waive an Agent subscription or other service requirements.
- Create one UUID and persist it with the exact JSON body before submission. Include model, image, video, mode (animate or replace), resolution (480P or 720P), and any optional prompt/seed/region. Do not include duration.
- Send that body to the selected quote route with Content-Type: application/json and x-request-id: UUID. A successful HTTP 200 response contains quote_token, request_id, expires_at and billing. Check request_id matches, then show the maximum charge for approval.
- Submit the same body and x-request-id to the matching generation route. Add x-modelrush-video-edit-quote: quote_token. Keep the same account, Agent run where applicable, region, source bytes and settings. Idempotency-Key does not replace this UUID or signature. Changing it cannot authorize an extra task under the same quote.
- Save the returned id and poll_url. Poll the returned route with its required credential. A video status route uses completed/failed; the unified prediction route uses succeeded/failed. Do not submit a second job to check progress.
Missing/invalid UUID or signature: HTTP 400 video_edit_quote_required. Expired quote, changed media/settings or changed price: HTTP 409 video_edit_quote_changed. Do not automatically accept a new maximum. Fetch a fresh quote with the same UUID and body after a definitive quote rejection, show it and confirm again. If the first submission has not been attempted and its quote expired, refresh before submitting. For a timeout, lost response or uncertain 5xx, preserve the original UUID, body and signature and retry that exact generation request once to recover its result. An already accepted matching request replays before quote expiry/media validation, so do not replace an expired token during uncertain recovery. If uncertainty remains, stop and investigate using the request ID; never switch UUID just to bypass it. HTTP 409 idempotency_conflict means the ID belongs to a different request; stop rather than overwrite it. Keep signed quotes private and do not log credentials.
Already accepted requests from before this change can replay with their original Idempotency-Key and retained body, including the old duration value. Replay returns the existing task and does not reserve or charge again. This compatibility is only for matching accepted tasks. It does not permit a new unsigned request, a changed request or a new UUID. If there is no known accepted task, migrate to the signed quote flow.
Download the runnable Node.js example at wan-animate-quoted-request.mjs. Set MODELRUSH_API_KEY for public, or MODELRUSH_AGENT_TOKEN for agent, on the server. State files contain the private quote token; keep them out of Git. The quote command never submits a generation. Replace MAX_CENTS with the displayed integer only after approval. The submit/recover commands can reserve credits and start a paid task. They make one request each and never auto-retry. refresh keeps the same UUID/body and requires a new review; use it only before the first submission or after a definitive video_edit_quote_changed response.
sh
PreviousPOST /videos/generations