The resolution enum has 8 values, but each Sume model takes 3 or 4

The resolution field on POST /v1/videos is an enum of eight values (360p, 480p, 720p, 768p, 1080p, 1K, 2K, 4K), but no video model takes more than four of them. Check your value against supported_resolutions from GET /v1/videos/models before you submit, or the answer is a 400.

Who takes what

The enum is shared across the API, which is why a valid enum value can still be wrong for the model. The sharpest case is MiniMax H3: its native sizes are 480p and 768p, so 720p is not on its list.

Totals below use each model's longest clip at the lowest and highest resolution.

Check before submit

One function covers resolution and length. It raises early with a message your user can read.

def check(model, res, seconds):
    if res not in model["supported_resolutions"]:
        raise ValueError(
            f"{model['id']}: {res} not in {model['supported_resolutions']}"
        )
    if seconds not in model["supported_durations"]:
        raise ValueError(f"{model['id']}: {seconds} s not supported")

# model = one entry of GET /v1/videos/models -> data[]

Gotchas

The 4K spelling is uppercase in the enum and in the Omni pricing key. Image models use a different set (512, 1K, 2K, 4K), so do not share one validator between the two APIs.

Models change: read the live array and cache it for minutes, not months.