Live Slicer

The Live Slicer API allows you to:

• Mark ads, replacement content, or content boundaries.
• Set metadata on an asset.
• Retrieve detailed Live Slicer status information.

The API is exposed via an internal web server in the Live Slicer and can be called from any programming language with an HTTP client interface.

Choosing Between Live Slicer API and Slicer API

API Conventions

• Uses POST or GET HTTP methods.
• Most endpoints do not require query string parameters.
• Request body must be a serialized JSON object.
• Responses include a JSON object with an error field:
  • 0 indicates success.
  • Non-zero values indicate errors, often accompanied by a msg field.

Authentication

Authentication is required for Live Slicer version 15091000 or higher. By default, authentication is disabled but can be enabled via the authenticated_api_port configuration parameter. Requests over this port are unencrypted.

Authentication Parameters

Finding Your API Key

1. Navigate to Integration Keys.
2. API keys are listed under the API Keys section.

Authentication Example

Sample Request (HTTP)

POST /content_start HTTP/1.1
Content-Type: application/json
Host: localhost:65009
Content-Length: 108

{
  "timestamp": 1438101883,
  "cnonce": 123,
  "sig": "49bQGXKTRYPQ5b22m89zKe1zcKk=",
  "start_timecode": "11:22:33;04"
}

Sample Request (Python)

import urllib2, hashlib, time, json, base64

secret = hashlib.sha1('XH7HtD8tR3993IxfbcqX0uhKnc-mYksmPxqM2z1a').hexdigest()
timestamp = int(time.time())
endpoint = '/content_start'
cnonce = 123
sig_input = f"{endpoint}:{timestamp}:{cnonce}:{secret}"
sig = base64.b64encode(hashlib.sha1(sig_input).digest())
body = json.dumps({"timestamp": timestamp, "cnonce": cnonce, "sig": sig })
request = urllib2.urlopen('http://localhost:65009/' + endpoint, body)
response = json.loads(request.read())

assert response['error'] == 0

Port Configuration

By default, the Live Slicer listens for API requests on port 65009. You can modify this by updating the api_port configuration setting.

Scheduling Actions

You can schedule when an API request takes effect using one of the following parameters:

Most Live Slicer API endpoints accept these parameters.

Timecode

start_timecode specifies the exact video frame where an action should occur. The format follows:

• Drop frame: hh:mm:ss;vf
• Non-drop frame: hh:mm:ss:vf

Example: 00:15:02;01 marks the second frame at 15 minutes and two seconds after midnight.

For UDP and RTMP sources, enable the useSystemClockAsTimecode setting.

Resolving Timecodes

• If the requested timecode exists in the capture delay buffer, the Live Slicer applies the action at that frame's presentation timestamp (PTS).
• If not, the Live Slicer applies the action at the oldest frame in the buffer.
• Configure the buffer duration via capture_delay.

Future Timecodes

Enable future_timecodes to schedule actions up to 12 hours in the future.

Scheduled Break Expiration

Configure the expiration of future breaks using future_break_expiration_minutes.

View or delete scheduled breaks via remove_break and list_breaks.

Relative Time Scheduling

An alternative to start_timecode is specifying relative time using:

Precedence Order: offset_time_ms > offset_from_now_ms > start_timecode

If none of these parameters are included, the action takes effect immediately.

Examples

Sample Request (HTTP)

POST /blackout HTTP/1.1
Content-Type: application/json
Host: localhost:65009
Content-Length: 33

{
  "start_timecode": "11:22:33;04"
}

Sample Response (HTTP)

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 12

{
  "error": 0
}

Sample Request (Python)

import urllib2, json

body = json.dumps({"start_timecode": "11:22:33;04"})
request = urllib2.urlopen('http://localhost:65009/blackout', body)
response = json.loads(request.read())

assert response['error'] == 0

Sample Request (cURL)

curl --data '{"start_timecode":"11:22:33;04"}' http://localhost:65009/blackout

Endpoints