Offline Session with Filepath

Example API

curl -X POST http://<ip-address>/api/v3/transcoding/from_filepath \
-H "Content-Type: application/json" \
-H "Authorization: Basic <API-ID/Secret>" \
-d '{
    "input_filepath": "<input-file-with-location>",
    "name": "s3bucketinput",
    "description": "",
    "output_file": {
        "template_id": <template-id>,
        "format": "hls",
        "path": "<output-location>"
    }
}'

<ip-address>

This is the IP address of the server

<API-ID/Secret>

See Generate Access Token to obtain API Token and Secret - Keep them save incase the next step does not work.

See Generate Authentication Method, this can be completed on the Bitstreams server

<input-file-with-location>

After mounting the S3 bucket find the location of the file that you want to transcode. This requires that it is the full absolute path. For example /mnt/s3bucket/test-folder/apple-test.mp4

<template-id>

Navigate to the template that you want to use, the URL address will contain the template id. For example if the URL is http://10.141.1.4/templates/9 then the ID will be 9

<output-location>

After mounting the S3bucket, find the location of where you want to save the transcoded file. This requires the absolute path, excluding /mnt. For example if the absolute path output location is /mnt/s3bucket-22/test-folder/apple-test-output/ then the location will be /s3bucket-22/test-folder/apple-test-output/

The final HLS files will be located will be /mnt/s3bucket-22/test-folder/apple-test-output/<name>/output/

Known Issues/changes

These issues/changes will be address in the next release:

• the <output-location> will be the full absolute path including /mnt
• the <output-location> will no longer automatically create <name>/output/