Skip to main content
POST
/
v1
/
text-to-video
Python
from magic_hour import Client
from os import getenv

client = Client(token=getenv("API_TOKEN"))
res = client.v1.text_to_video.generate(
    end_seconds=5.0,
    orientation="landscape",
    style={"prompt": "a dog running"},
    name="Text To Video video",
    resolution="720p",
    wait_for_completion=True,
    download_outputs=True,
    download_directory="."
)
{
  "id": "cuid-example",
  "credits_charged": 450
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <api_key>, where <api_key> is your API key. To get your API key, go to Developer Hub and click "Create new API Key".

Body

application/json

Body

​
end_seconds
number<float>
required

The total duration of the output video in seconds. Supported durations depend on the chosen model:

  • ltx-2: 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30
  • seedance: 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
  • kling-2.5: 5, 10
  • kling-3.0: 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
  • sora-2: 4, 8, 12, 24, 36, 48, 60
  • veo3.1: 4, 6, 8, 16, 24, 32, 40, 48, 56

Legacy models:

  • kling-1.6: 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60
Required range: 2 <= x <= 60
Example:

5

​
style
object
required
​
name
string
default:Text To Video - dateTime

Give your video a custom name for easy identification.

Example:

"My Text To Video video"

​
aspect_ratio
enum<string>

Determines the aspect ratio of the output video.

  • ltx-2: Supports 9:16, 16:9, 1:1.
  • seedance: Supports 9:16, 16:9, 1:1.
  • kling-2.5: Supports 9:16, 16:9, 1:1.
  • kling-3.0: Supports 9:16, 16:9, 1:1.
  • sora-2: Supports 9:16, 16:9.
  • veo3.1: Supports 9:16, 16:9.

Legacy models:

  • kling-1.6: Supports 9:16, 16:9, 1:1.
Available options:
16:9,
9:16,
1:1
Example:

"16:9"

​
resolution
enum<string>

Controls the output video resolution. Defaults to 720p on paid tiers and 480p on free tiers.

  • ltx-2: Supports 480p, 720p, 1080p.
  • seedance: Supports 480p, 720p, 1080p.
  • kling-2.5: Supports 720p, 1080p.
  • kling-3.0: Supports 720p, 1080p.
  • sora-2: Supports 720p.
  • veo3.1: Supports 720p, 1080p.

Legacy models:

  • kling-1.6: Supports 720p, 1080p.
Available options:
480p,
720p,
1080p
Example:

"720p"

​
model
enum<string>
default:default

The AI model to use for video generation.

  • default: uses our currently recommended model for general use. For paid tiers, defaults to kling-2.5. For free tiers, it defaults to ltx-2.
  • ltx-2: Great for fast iteration with audio, lip-sync, and expressive faces
  • seedance: Great for fast iteration and start/end frame
  • kling-2.5: Great for motion, action, and camera control
  • kling-3.0: Great for cinematic, multi-scene storytelling with control
  • sora-2: Great for story-telling, dialogue & creativity
  • veo3.1: Great for realism, polish, & prompt adherence

Legacy models:

  • kling-1.6: Great for dependable clips with smooth motion

If you specify the deprecated model value that includes the -audio suffix, this will be the same as included audio as true.

Available options:
default,
ltx-2,
seedance,
kling-2.5,
kling-3.0,
veo3.1,
sora-2,
kling-1.6,
kling-2.5-audio,
veo3.1-audio
Example:

"kling-2.5-audio"

​
audio
boolean

Whether to include audio in the video. Defaults to false if not specified.

Audio support varies by model:

  • ltx-2: Automatically included with no extra credits
  • seedance: Not supported
  • kling-2.5: Automatically included with no extra credits
  • kling-3.0: Toggle-able (can enable/disable)
  • sora-2: Automatically included with no extra credits
  • veo3.1: Toggle-able (can enable/disable)

Legacy models:

  • kling-1.6: Not supported
Example:

true

Response

Success

Success

​
id
string
required

Unique ID of the video. Use it with the Get video Project API to fetch status and downloads.

Example:

"cuid-example"

​
credits_charged
integer
required

The amount of credits deducted from your account to generate the video. If the status is not 'complete', this value is an estimate and may be adjusted upon completion based on the actual FPS of the output video.

If video generation fails, credits will be refunded, and this field will be updated to include the refund.

Example:

450