You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/api-references/video-models/bytedance/seedance-1.0-lite-image-to-video.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,15 +37,16 @@ Below, you can find both corresponding API schemas.
37
37
38
38
## API Schemas
39
39
40
+
{% hint style="success" %}
41
+
Now, all of our API schemas for video models use our new universal short URL — `https://api.aimlapi.com/v2/video/generations`. \
42
+
However, you can still call this model using the legacy URL that includes the vendor name.
43
+
{% endhint %}
44
+
40
45
### Create a video generation task and send it to the server
41
46
42
47
You can generate a video using this API. In the basic setup, you only need a reference image and a prompt. This endpoint creates and sends a video generation task to the server — and returns a generation ID.
43
48
44
-
{% hint style="success" %}
45
-
To quickly test video models from different developers without changing endpoints, use our new universal short one — **`https://api.aimlapi.com/v2/video/generations`.**
@@ -54,8 +55,8 @@ To quickly test video models from different developers without changing endpoint
54
55
After sending a request for video generation, this task is added to the queue. This endpoint lets you check the status of a video generation task using its `id`, obtained from the endpoint described above.\
55
56
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
Copy file name to clipboardExpand all lines: docs/api-references/video-models/bytedance/seedance-1.0-lite-text-to-video.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,16 +37,17 @@ Below, you can find both corresponding API schemas.
37
37
38
38
## API Schemas
39
39
40
+
{% hint style="success" %}
41
+
Now, all of our API schemas for video models use our new universal short URL — `https://api.aimlapi.com/v2/video/generations`. \
42
+
However, you can still call this model using the legacy URL that includes the vendor name.
43
+
{% endhint %}
44
+
40
45
### Create a video generation task and send it to the server
41
46
42
47
You can generate a video using this API. In the basic setup, you only need a prompt.\
43
48
This endpoint creates and sends a video generation task to the server — and returns a generation ID.
44
49
45
-
{% hint style="success" %}
46
-
To quickly test video models from different developers without changing endpoints, use our new universal short one — **`https://api.aimlapi.com/v2/video/generations`.**
@@ -55,8 +56,8 @@ To quickly test video models from different developers without changing endpoint
55
56
After sending a request for video generation, this task is added to the queue. This endpoint lets you check the status of a video generation task using its `id`, obtained from the endpoint described above.\
56
57
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
<div align="left"><figure><img src="../../../.gitbook/assets/seedance_t2v_preview.gif" alt=""><figcaption><p><code>"A menacing evil dragon appears in a distance above the tallest mountain, then</code><br><code>rushes toward the camera with its jaws open, revealing massive fangs. We see it's coming."</code></p></figcaption></figure></div>
314
+
<div align="left"><figure><img src="../../../.gitbook/assets/seedance_t2v_preview.gif" alt=""><figcaption><p><code>"A menacing evil dragon appears in a distance above the tallest mountain, then</code><br><code>rushes toward the camera with its jaws open, revealing massive fangs. We see it's coming."</code></p></figcaption></figure></div>
Copy file name to clipboardExpand all lines: docs/api-references/video-models/bytedance/seedance-1.0-pro-image-to-video.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,15 +55,16 @@ Below, you can find both corresponding API schemas.
55
55
56
56
## API Schemas
57
57
58
+
{% hint style="success" %}
59
+
Now, all of our API schemas for video models use our new universal short URL — `https://api.aimlapi.com/v2/video/generations`. \
60
+
However, you can still call this model using the legacy URL that includes the vendor name.
61
+
{% endhint %}
62
+
58
63
### Create a video generation task and send it to the server
59
64
60
65
You can generate a video using this API. In the basic setup, you only need a reference image and a prompt. This endpoint creates and sends a video generation task to the server — and returns a generation ID.
61
66
62
-
{% hint style="success" %}
63
-
To quickly test video models from different developers without changing endpoints, use our new universal short one — **`https://api.aimlapi.com/v2/video/generations`.**
@@ -72,8 +73,8 @@ To quickly test video models from different developers without changing endpoint
72
73
After sending a request for video generation, this task is added to the queue. This endpoint lets you check the status of a video generation task using its `generation_id`, obtained from the endpoint described above.\
73
74
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
Copy file name to clipboardExpand all lines: docs/api-references/video-models/bytedance/seedance-1.0-pro-text-to-video.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,16 +54,17 @@ Below, you can find both corresponding API schemas.
54
54
55
55
## API Schemas
56
56
57
+
{% hint style="success" %}
58
+
Now, all of our API schemas for video models use our new universal short URL — `https://api.aimlapi.com/v2/video/generations`. \
59
+
However, you can still call this model using the legacy URL that includes the vendor name.
60
+
{% endhint %}
61
+
57
62
### Create a video generation task and send it to the server
58
63
59
64
You can generate a video using this API. In the basic setup, you only need a prompt.\
60
65
This endpoint creates and sends a video generation task to the server — and returns a generation ID.
61
66
62
-
{% hint style="success" %}
63
-
To quickly test video models from different developers without changing endpoints, use our new universal short one — **`https://api.aimlapi.com/v2/video/generations`.**
@@ -72,8 +73,8 @@ To quickly test video models from different developers without changing endpoint
72
73
After sending a request for video generation, this task is added to the queue. This endpoint lets you check the status of a video generation task using its `generation_id`, obtained from the endpoint described above.\
73
74
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
0 commit comments