Skip to main content
Beta. The Video API is in beta.
The API is versioned in its path: /v1/prediction. Everything on this page describes how /v1 evolves. A change that cannot be made compatibly gets a new version path, not a silent edit to this one.

​
The rule that decides everything

Every capability’s parameter schema sets additionalProperties: false. The engine rejects an unknown key before any compute runs, at $0. That single fact determines which direction of change is safe. Widening what we accept can never break a request you already send. Narrowing it can, because a request that validates today may stop validating tomorrow.

​
Compatible changes — shipped without notice

These land continuously and are recorded in the changelog.
Parse responses so that unknown fields are ignored. Most JSON clients do this by default; strict deserializers configured to fail on unknown keys do not. If yours is strict, turn that off for our responses — we treat response-field additions as compatible and will keep making them.

​
Breaking changes — 90 days’ notice

For any of these we give 90 days’ notice before the change takes effect. Notice goes by email to the organizations whose recent traffic is actually affected, and is published in the changelog. The deprecated behaviour keeps working for the full window. Two things we do not treat as breaking, and you should not rely on: the exact bytes of an output file, and the wall-clock duration of a job. Encoder versions and infrastructure change; a byte-identical re-render is not part of the contract. Assert on media properties — duration, resolution, codec, stream count — not on file hashes.

​
Security exception

A change that closes a security or content-safety hole ships as fast as the risk requires, without the 90-day window. We tell affected organizations what changed and why as soon as we can, and we keep such changes as narrow as the problem allows.

​
What “beta” changes

The beta label is about the rate card and the capability set, not about the request contract. Already stable, and covered by the notice policy above:
  • The submit-and-poll flow, the prediction object, and the terminal statuses.
  • Request shape: capability, input_url / input_urls, params, output_format.
  • Parameter names, bounds, and enums for the documented capabilities.
  • error_code values and the $0-reject guarantees in Billing & Limits.
Still moving during beta:
  • Pricing. Rates may change with shorter notice than 90 days. Current rates are always in Billing & Limits.
  • New capabilities, which arrive continuously.
We do not remove a documented capability during beta without the full 90-day window. Beta means the surface grows and the price may move; it does not mean the ground shifts under a request you already ship.

​
Staying informed

Watch the changelog for every compatible and breaking change. Deprecation notices additionally go by email to affected organizations, so keep a monitored address on your account — it is the only channel that reaches you directly.
Last modified on August 13, 2026