After the API Key, Input, and ProfileSet for your encoding configuration are ready, you should determine Queue type and target file destination. (About Queue type, please check Smart Queue and Priority Queue to learn more.)
Fire a HTTP request of creating Job via curl command like below:
curl -X POST 'https://api.az.blendvision.io/api/v1/job' \
--header 'X-API-KEY: {{apiKey}}' \
--header 'Content-Type: application/json' \
--data-raw '{
"input_id": "{{inputID}}",
"profile_set_id": "{{profileSetID}}",
"queue": "pq",
"url": "https://fakeaccount.blob.core.windows.net/container-path/vodfile.mp4"
}'
In the request,
- --header 'X-API-KEY: {{apiKey}}' Header API Key authorization.
- "input_id": "{{inputID}}" specify an Input for pulling source.
- "profile_set_id": "{{profileSetID}}" specify ProfileSet.
- "queue": "pq", use Priority Queue
- "url": "https://fakea..." specify the target source video to be transcoded
Replace the {{apiKey}}, {{inputID}}, {{profileSetID}} with what you have prepared in the previous session.
You’ll get the following response (in JSON format) if the input parameters are unmistakable.
{
job_id: "374eb19e-e5d6-4149-bf8f-159b82059081"
}
The encoding process is running asynchronized in BlendVision Encoder server. The ID of a new Job is returned in the response body.