Passthrough of Live Event GET Commands - AWS Elemental Conductor Live 3

This is version 3.19 of the AWS Elemental Conductor Live 3 documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor Live 3 Documentation.

Passthrough of Live Event GET Commands

HTTP Request and Response

Request URL

GET http://<Conductor IP address> /channels/<ID of channel>/live_events/<action>

where:

  • ID of channel is the ID of a channel known to the AWS Elemental Conductor Live 3 API.

  • /live_events/<action> is the command from the AWS Elemental Live API. See below for a list.

When the command is submitted, the AWS Elemental Conductor Live 3 API determines the Live event that corresponds to the Conductor channel, then submits the appropriately formed command to the Live API.

Action Signature in AWS Elemental Live Signature in AWS Elemental Conductor Live 3
GET /live_events/<id>/inputs /channels/<ID of channel>/live_events/inputs

Call Header

  • Accept: Set to application/xml

  • Content-Type: Set to application/xml

If you are implementing user authentication, you must also include three authorization headers; see Header Content for User Authentication.

Request Body

Include a body only if the original AWS Elemental Live command includes a body. Format the body in exactly the same way.

Response

The response repeats back the response received from the Live API, exactly as received from that API.

Example

AWS Elemental Live REST call:

GET http:/live_events/13/inputs

AWS Elemental Conductor Live 3 passthrough of this call:

GET http://192.0.2.16/channels/13/live_events/inputs