MOmoda
media

Upscale Video

Changed on

Deterministic video super-resolution to a target resolution (metered; long-running).

One video in, a higher-resolution new file out — the input is never modified and the result records it as its lineage parent. No prompt and no model choice: the serving engine is a Moda-side table entry. Inputs longer than the per-upscale duration cap, already at/above the target, or above the per-upscale cost ceiling are rejected before anything is paid for.

Like generate-video, the provider render runs within this call (can take minutes). The response's applied block reports the delivered resolution; adjustments lists any snap away from the exact ask.

post/media/upscale-video

Request

  • Base URL
    https://api.moda.app/v1
  • URL
    https://api.moda.app/v1/media/upscale-video
  • Auth
    HTTP bearer

Headers

Moda-Version'2026-04-12' | '2026-05-01'
Example:2026-05-01

Calendar-dated API version pin. New integrations should pin 2026-05-01 to opt into the newest response shapes. For back-compat the server also accepts requests with no header and resolves them to the current default (today: 2026-04-12); that default advances on each sunset date. Any unsupported value returns 400 unsupported_version.

Request body

videostring required

The video to upscale: a file_ id from an upload or an http(s) video URL.

target_resolutionstring

One of 720p, 1080p, 1440p, 2160p. Pick the smallest that meets the need — cost scales with it.

idempotency_keystring nullable

Keys the provider-job checkpoint: a retried call with the same key resumes the existing upscale instead of paying for a duplicate.

Response

Successful Response

object required

Changes