Skip to content

AVO processing steps

Below are the stesps to process/optimize the videos using N7 AVO.

For demo purpose, we will be using www.nviztest.com domain as an example.
We will process a video from source-domain (static.nviztest.com):
e.g. https://static.nviztest.com/videos/vid101.mp4
After processing, it will then be accessible on target-domain (www.nviztest.com) with the same path as source:
i.e. https://www.nviztest.com/videos/vid101.mp4

Prerequisite

  1. You must have an account on Nitrogen.

  2. Your target domain on which you want to configure AVO must have been registered on Nitrogen.

  3. You must have a service account configured with Editor access. If not, you can refer this article for the same.

  4. Your source video domain and target domain must be different.

Steps

  1. Use the below API to process the video (provide correct source-domain and auth-token):

    curl --request POST --location 'https://dash.n7.io/api/v2/transcoder/video/tasks' \
--header 'Authorization: Token <api-key-of-service-account>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "domain": "www.nviztest.com",
    "mediaPath": "https://static.nviztest.com/videos/vid101.mp4",
    "callbackUrl": "https://static.nviztest.com/callback/status/endpoint"
}'

    callbackUrl: A URL that will be called upon the successful processing of the videos, providing the relevant status. This parameter is optional.
    Please pre-process all the videos before using them on actual domain, or enabling AVO - otherwise AVO will return 404 for them.

  2. Setup the video routing pattern for AVO on Video route page, and Deploy the changes.

  3. Test the video on target domain after 10 mins. In this case check:
    https://www.nviztest.com/videos/vid101.mp4
    You can also verify the video variant creation status on Video catalog page.

Notes

  • Note down the task-Id returned by API. So that, for any issues, you can provide it as reference to us.