Hi @jess
I forgot to mention a few things.
-
videoid.value does contain a valid entryID. This isn’t in the code example, but I’ve verified that it’s true. I’ve also tried hard-coding a entry ID in the Update call to see if the behavior changes It does not.
-
When I consult the Kaltura_api_v3.log for more information, I don’t see any information relating to the request. I’ve altered the client tag to make finding the appropriate entries in the log but that client tag does not appear in the api log.
-
I’ve used Fiddler locally to examine the http traffic between my local dev server and the kaltura servers. I can see the request to the update endpoint. the request looks correct. There is an entryId parameter
Here is the body of the request. I am just noticing that the request is missing some closing brackets. If manually place them in the request, it seems to actually work.
POST http://kaltura-prod.intranet.hdr/api_v3/service/media/action/update HTTP/1.1
Accept: application/xml
Content-Type: application/json
Host: kalturahost.domain.hdr
Content-Length: 782
Expect: 100-continue
Accept-Encoding: gzip, deflate
Pragma: akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-check-cacheable, akamai-x-get-cache-key, akamai-x-get-true-cache-key, akamai-x-get-ssl-client-session-id, akamai-x-serial-no, akamai-x-get-request-id
{“apiVersion”:“3.3.0”,“clientTag”:“TV-EditVideo”,“entryId”:“0_ct3a8t3g”,“format”:2,“kalsig”:“kalsighere”,“ks”:“ks-redacted”,“mediaEntry”:{“categories”:“category”,“description”:“description”,“name”:“video name”,“objectType”:“KalturaMediaEntry”,“tags”:“tags”
The response looks like this
<?xml version="1.0" encoding="utf-8"?><xml><result><error><code>MISSING_MANDATORY_PARAMETER</code><message>Missing parameter "entryId"</message><objectType>KalturaAPIException</objectType><args><item><objectType>KalturaApiExceptionArg</objectType><name>PARAM_NAME</name><value>entryId</value></item></args></error></result><executionTime>0.0032801628112793</executionTime></xml>