Create Videos
Using this endpoint you can create the videos in bulk, by passing the tags and their values in request body as payload.
This endpoint returns a list of URLs along with inference_id and the unique_id that was part of the payload. Videos can be downloaded from these URLs. The video generation process is asynchronous and hence the user needs to wait for a period of time before the links become functional. The pause time, depends on the number of videos to be generated. We can get status of videos by two ways:
- Setting Webhook
- Pinging our video_status api with the inference_id (from the response of create_video api)
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
To create the videos, we need the project_id, which is the unique identifier for a user's project in our systems.
Body
The payload is a list of dictionaries, where all the parameters required for video generation have to provided along with a unique_id.
Eg.
[
{
"names": "Manash",
"unique_id": "abc123"
},
{
"names": "Manash2",
"unique_id": "cba321"
}
]
In the example, we have used the tags: names and unique_id, depending on the case the individual query parameters would change.
Response
S3 url for the video file.
S3 url for the audio file.
inference_id is a unique identifer to map the generated videos with the users.
project_id is a unique identifier for a project created by the user. In a project, multiple inference videos can be generated.
This corresponds to the unique_id sent in the request body. It can be used by the user's to uniquely identify the generation status for a video with the particular tags.
These are the links to videos hosted on our landing page.
Permalinks are links to the generated inferences that do not expire.
This corresponds to the url for the thumbnail of the generated video.