In this article we provide examples of calls and responses relative to creating Reach vendor tasks.
Creating a Reach vendor task
Example of a request using entryVendorTask.get - Kaltura VPaaS API Documentation:
curl -X POST https://www.kaltura.com/api_v3/service/reach_entryvendortask/action/add \
-d "ks=$KALTURA_SESSION" \
-d "entryVendorTask[catalogItemId]=35316516" \
-d "entryVendorTask[entryId]=1_bk35mi5t" \
-d "entryVendorTask[externalTaskId]=65464653" \
-d "entryVendorTask[partnerData]=ifneeded" \
-d "entryVendorTask[reachProfileId]=654651" \
-d "entryVendorTask[objectType]=KalturaEntryVendorTask"When creating a vendor task following processing a prior Reach vendor task, you should use the access token of the prior task as the KS. In such case, also make sure that you are passing the same values of the entryId and reachProfileId.
And in all cases, you need to pass a catalogItemId corresponding to the service you want to create a job for.
Example of a response after creating a task with the REACH profile information for a captions task using entryVendorTask.get - Kaltura VPaaS API Documentation:
{
"id": "602371791",
"partnerId": 4171212,
"vendorPartnerId": 1420622,
"createdAt": 1767972617,
"updatedAt": 1767972617,
"queueTime": 1767972617,
"entryId": "1_bk35mi5t",
"status": 1,
"reachProfileId": 654651,
"catalogItemId": 35316516,
"price": 6,
"userId": "",
"entryObjectType": 1,
"accessKey": "djJ8NjE3MTI5MnweTxH1xX1MsUL_ekjD1Arotj-yHG4QdEd3Z28sFaFvm2UImhSIX1GTPeEeiDdnYfWhy5VPcIxIB2RpTcKr6x16PrCzrCCE8QwMo8d-_GxElpwghRuZOHDow9HHEp3d6gCBLZjEi1H24NXAdQaK9faIRGkicjWCEmAs3JuHdxoTAp554Low9wh_aBwwAA5sJf60y6EZqcXZ4R1-pRJswBS750GgFpU9zDgH4EFojpWcAg==",
"version": 11,
"creationMode": 1,
"expectedFinishTime": 1768491017,
"serviceType": 1,
"serviceFeature": 1,
"turnAroundTime": 4,
"objectType": "KalturaEntryVendorTask"
}