Skip to content

Commit 44f7b51

Browse files
techpro-aimlapigitbook-bot
authored andcommitted
GITBOOK-705: docs: re-connect all veo2 and veo3 schemas, add hint
1 parent 6587751 commit 44f7b51

6 files changed

Lines changed: 48 additions & 42 deletions

File tree

docs/api-references/video-models/google/veo-3-fast-image-to-video.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -37,15 +37,16 @@ Below, you can find two corresponding API schemas and examples for both endpoint
3737

3838
## API Schemas
3939

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+
4045
### Create a video generation task and send it to the server
4146

4247
You can generate a video using this API.
4348

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`.**
46-
{% endhint %}
47-
48-
{% openapi-operation spec="veo-3-0-i2v-fast" path="/v2/generate/video/google/generation" method="post" %}
49+
{% openapi-operation spec="veo-3-0-i2v-fast" path="/v2/video/generations" method="post" %}
4950
[OpenAPI veo-3-0-i2v-fast](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo-3.0-i2v-fast.json)
5051
{% endopenapi-operation %}
5152

@@ -54,8 +55,8 @@ To quickly test video models from different developers without changing endpoint
5455
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.\
5556
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
5657

57-
{% openapi-operation spec="veo3-fetch" path="/v2/generate/video/google/generation" method="get" %}
58-
[OpenAPI veo3-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo3-pair.json)
58+
{% openapi-operation spec="universal-video-endpoint-fetch" path="/v2/video/generations" method="get" %}
59+
[OpenAPI universal-video-endpoint-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/ByteDance/omnihuman-pair.json)
5960
{% endopenapi-operation %}
6061

6162
## Full Example: Generating and Retrieving the Video From the Server

docs/api-references/video-models/google/veo-3-fast-text-to-video.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -37,15 +37,16 @@ Below, you can find two corresponding API schemas and an example with both endpo
3737

3838
## API Schemas
3939

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+
4045
### Create a video generation task and send it to the server
4146

4247
You can generate a video using this API. In the basic setup, you only need a prompt.
4348

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`.**
46-
{% endhint %}
47-
48-
{% openapi-operation spec="veo-3-0-fast" path="/v2/generate/video/google/generation" method="post" %}
49+
{% openapi-operation spec="veo-3-0-fast" path="/v2/video/generations" method="post" %}
4950
[OpenAPI veo-3-0-fast](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo-3.0-fast.json)
5051
{% endopenapi-operation %}
5152

@@ -54,8 +55,8 @@ To quickly test video models from different developers without changing endpoint
5455
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.\
5556
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
5657

57-
{% openapi-operation spec="veo3-fetch" path="/v2/generate/video/google/generation" method="get" %}
58-
[OpenAPI veo3-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo3-pair.json)
58+
{% openapi-operation spec="universal-video-endpoint-fetch" path="/v2/video/generations" method="get" %}
59+
[OpenAPI universal-video-endpoint-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/ByteDance/omnihuman-pair.json)
5960
{% endopenapi-operation %}
6061

6162
## Full Example: Generating and Retrieving the Video From the Server

docs/api-references/video-models/google/veo-3-image-to-video.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -37,15 +37,16 @@ Below, you can find two corresponding API schemas and examples for both endpoint
3737

3838
## API Schemas
3939

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+
4045
### Create a video generation task and send it to the server
4146

4247
You can generate a video using this API.
4348

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`.**
46-
{% endhint %}
47-
48-
{% openapi-operation spec="veo-3-0-i2v" path="/v2/generate/video/google/generation" method="post" %}
49+
{% openapi-operation spec="veo-3-0-i2v" path="/v2/video/generations" method="post" %}
4950
[OpenAPI veo-3-0-i2v](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo-3.0-i2v.json)
5051
{% endopenapi-operation %}
5152

@@ -54,8 +55,8 @@ To quickly test video models from different developers without changing endpoint
5455
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.\
5556
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
5657

57-
{% openapi-operation spec="veo3-fetch" path="/v2/generate/video/google/generation" method="get" %}
58-
[OpenAPI veo3-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo3-pair.json)
58+
{% openapi-operation spec="universal-video-endpoint-fetch" path="/v2/video/generations" method="get" %}
59+
[OpenAPI universal-video-endpoint-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/ByteDance/omnihuman-pair.json)
5960
{% endopenapi-operation %}
6061

6162
## Full Example: Generating and Retrieving the Video From the Server

docs/api-references/video-models/google/veo2-image-to-video.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -33,15 +33,16 @@ Below, you can find both corresponding API schemas.
3333

3434
## API Schemas
3535

36+
{% hint style="success" %}
37+
Now, all of our API schemas for video models use our new universal short URL — `https://api.aimlapi.com/v2/video/generations`. \
38+
However, you can still call this model using the legacy URL that includes the vendor name.
39+
{% endhint %}
40+
3641
### Create a video generation task and send it to the server
3742

3843
You can generate a video using this API.
3944

40-
{% hint style="success" %}
41-
To quickly test video models from different developers without changing endpoints, use our new universal short one — **`https://api.aimlapi.com/v2/video/generations`.**
42-
{% endhint %}
43-
44-
{% openapi-operation spec="veo2-image-to-video" path="/v2/generate/video/google/generation" method="post" %}
45+
{% openapi-operation spec="veo2-image-to-video" path="/v2/video/generations" method="post" %}
4546
[OpenAPI veo2-image-to-video](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/Veo2-Image-to-Video.json)
4647
{% endopenapi-operation %}
4748

@@ -50,8 +51,8 @@ To quickly test video models from different developers without changing endpoint
5051
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.\
5152
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
5253

53-
{% openapi-operation spec="veo3-fetch" path="/v2/generate/video/google/generation" method="get" %}
54-
[OpenAPI veo3-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo3-pair.json)
54+
{% openapi-operation spec="universal-video-endpoint-fetch" path="/v2/video/generations" method="get" %}
55+
[OpenAPI universal-video-endpoint-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/ByteDance/omnihuman-pair.json)
5556
{% endopenapi-operation %}
5657

5758
## Full Example: Generating and Retrieving the Video From the Server

docs/api-references/video-models/google/veo2-text-to-video.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -33,15 +33,16 @@ Below, you can find both corresponding API schemas.
3333

3434
## API Schemas
3535

36+
{% hint style="success" %}
37+
Now, all of our API schemas for video models use our new universal short URL — `https://api.aimlapi.com/v2/video/generations`. \
38+
However, you can still call this model using the legacy URL that includes the vendor name.
39+
{% endhint %}
40+
3641
### Create a video generation task and send it to the server
3742

3843
You can generate a video using this API. In the basic setup, you only need a prompt, the aspect ratio, and the desired duration (5, 6, 7, or 8 seconds).
3944

40-
{% hint style="success" %}
41-
To quickly test video models from different developers without changing endpoints, use our new universal short one — **`https://api.aimlapi.com/v2/video/generations`.**
42-
{% endhint %}
43-
44-
{% openapi-operation spec="veo2" path="/v2/generate/video/google/generation" method="post" %}
45+
{% openapi-operation spec="veo2" path="/v2/video/generations" method="post" %}
4546
[OpenAPI veo2](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo2.json)
4647
{% endopenapi-operation %}
4748

@@ -50,8 +51,8 @@ To quickly test video models from different developers without changing endpoint
5051
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.\
5152
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
5253

53-
{% openapi-operation spec="veo3-fetch" path="/v2/generate/video/google/generation" method="get" %}
54-
[OpenAPI veo3-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo3-pair.json)
54+
{% openapi-operation spec="universal-video-endpoint-fetch" path="/v2/video/generations" method="get" %}
55+
[OpenAPI universal-video-endpoint-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/ByteDance/omnihuman-pair.json)
5556
{% endopenapi-operation %}
5657

5758
## Full Example: Generating and Retrieving the Video From the Server

docs/api-references/video-models/google/veo3-text-to-video.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -33,15 +33,16 @@ Below, you can find both corresponding API schemas.
3333

3434
## API Schemas
3535

36+
{% hint style="success" %}
37+
Now, all of our API schemas for video models use our new universal short URL — `https://api.aimlapi.com/v2/video/generations`. \
38+
However, you can still call this model using the legacy URL that includes the vendor name.
39+
{% endhint %}
40+
3641
### Create a video generation task and send it to the server
3742

3843
You can generate a video using this API. In the basic setup, you only need a prompt.
3944

40-
{% hint style="success" %}
41-
To quickly test video models from different developers without changing endpoints, use our new universal short one — **`https://api.aimlapi.com/v2/video/generations`.**
42-
{% endhint %}
43-
44-
{% openapi-operation spec="veo3" path="/v2/generate/video/google/generation" method="post" %}
45+
{% openapi-operation spec="veo3" path="/v2/video/generations" method="post" %}
4546
[OpenAPI veo3](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo3.json)
4647
{% endopenapi-operation %}
4748

@@ -50,8 +51,8 @@ To quickly test video models from different developers without changing endpoint
5051
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.\
5152
If the video generation task status is `complete`, the response will include the final result — with the generated video URL and additional metadata.
5253

53-
{% openapi-operation spec="veo3-fetch" path="/v2/generate/video/google/generation" method="get" %}
54-
[OpenAPI veo3-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/Google/veo3-pair.json)
54+
{% openapi-operation spec="universal-video-endpoint-fetch" path="/v2/video/generations" method="get" %}
55+
[OpenAPI universal-video-endpoint-fetch](https://raw.githubusercontent.com/aimlapi/api-docs/refs/heads/main/docs/api-references/video-models/ByteDance/omnihuman-pair.json)
5556
{% endopenapi-operation %}
5657

5758
## Full Example: Generating and Retrieving the Video From the Server

0 commit comments

Comments
 (0)