Setup and Using ESNI

setup the esni server to leverage zixi’s esni implementation, please request that esni be enabled for your account by your zixi account team once done, valid esni/scte 224 element xml payloads can be added to the esni database via http put url endpoint the production url is https //esni zen zixi com/ \<customer zenmaster prefix>/ authentication per esni standard, use https //docs aws amazon com/iam/latest/userguide/reference sigv html access key and secret key can be rotated by request reach out to your zixi account rep as required http methods put – adding a new xml payload to the database / updating the xml payload in the database delete – removing an xml payload from the database get – retrieving xml payloads from the database xml http put ordering within the xml payloads are hrefs that reference other media elements referenced xmls must be added to the database prior to broadcasting the media that references these xmls audience viewingpolicy policy media working with esni elements media , policy , viewingpolicy , and audience all have @lastupdated xml attributes these must be updated each time a new esni element is posted if @lastupdated is older than what is currently in the database, the xml will not update tip when using postman use this variable lastupdated="{{$isotimestamp}}" to ensure current time stamp adding an esni element put https //esni zen zixi com/ {customer zenmaster prefix} / {element} / id/of/element body xml formatted media when creating the other esni elements, replace “{element}” from the url above with the esni element type – media , policy , viewingpolicy , audience modifying/viewing an esni element put/get https //esni zen zixi com/ {customer zenmaster prefix}/{element} /id/of/element body for put xml formatted media with edits and updated \<lastupdated> value deleting an esni element delete https //esni zen zixi com/ {customer zenmaster prefix}/{element} /id/of/element body empty viewing all elements of a certain type in the database get https //esni zen zixi com/ {customer zenmaster prefix} /?role= {element} replace “ {element} ” from the url above with a capitalized version of the esni element type – media , policy , viewingpolicy , audience validating esni element xml put https //esni zen zixi com/ {customer zenmaster prefix} / validate body xml formatted media this request will return any errors in the xml preventing a successful upload checking zixi esni decisioning service version get https //esni zen zixi com/ {customer zenmaster prefix} / status/about body empty configuration notes audience tags by default, the zixi esni backend will only be aware of audience id’s, vird tags and dma tags for associating zen master targets with audience files for timing optimization purposes options can be added as needed upid formats by default, scte 224 upid asserts will match with scte 35 payloads presented in hex, base64, or text if your deployment requires this to be limited to a specific format, this can be arranged schedule offset depending on upstream workflows, streaming latency can cause a timing disparity between utc schedule timing and currently displayed content on the stream an offset can be applied so that matchtime and scte 35 effective windows align with video stream