Amazon MediaLive · Schema

CreateInputRequest

The name of the input

BroadcastingMedia ProcessingMedia

Properties

Name Type Description
Destinations object
InputDevices object
InputSecurityGroups object
MediaConnectFlows object
Name object
RequestId object
RoleArn object
Sources object
Tags object
Type object
Vpc object
View JSON Schema on GitHub

JSON Schema

medialive-api-create-input-request-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/amazon-medialive/refs/heads/main/json-schema/medialive-api-create-input-request-schema.json",
  "title": "CreateInputRequest",
  "description": "The name of the input",
  "type": "object",
  "properties": {
    "Destinations": {
      "allOf": [
        {
          "$ref": "#/components/schemas/__listOfInputDestinationRequest"
        },
        {
          "xml": {
            "name": "destinations"
          },
          "description": "Destination settings for PUSH type inputs."
        }
      ]
    },
    "InputDevices": {
      "allOf": [
        {
          "$ref": "#/components/schemas/__listOfInputDeviceSettings"
        },
        {
          "xml": {
            "name": "inputDevices"
          },
          "description": "Settings for the devices."
        }
      ]
    },
    "InputSecurityGroups": {
      "allOf": [
        {
          "$ref": "#/components/schemas/__listOf__string"
        },
        {
          "xml": {
            "name": "inputSecurityGroups"
          },
          "description": "A list of security groups referenced by IDs to attach to the input."
        }
      ]
    },
    "MediaConnectFlows": {
      "allOf": [
        {
          "$ref": "#/components/schemas/__listOfMediaConnectFlowRequest"
        },
        {
          "xml": {
            "name": "mediaConnectFlows"
          },
          "description": "A list of the MediaConnect Flows that you want to use in this input. You can specify as few as one\nFlow and presently, as many as two. The only requirement is when you have more than one is that each Flow is in a\nseparate Availability Zone as this ensures your EML input is redundant to AZ issues.\n"
        }
      ]
    },
    "Name": {
      "allOf": [
        {
          "$ref": "#/components/schemas/__string"
        },
        {
          "xml": {
            "name": "name"
          },
          "description": "Name of the input."
        }
      ]
    },
    "RequestId": {
      "allOf": [
        {
          "$ref": "#/components/schemas/__string"
        },
        {
          "xml": {
            "name": "requestId"
          },
          "description": "Unique identifier of the request to ensure the request is handled\nexactly once in case of retries.\n"
        }
      ]
    },
    "RoleArn": {
      "allOf": [
        {
          "$ref": "#/components/schemas/__string"
        },
        {
          "xml": {
            "name": "roleArn"
          },
          "description": "The Amazon Resource Name (ARN) of the role this input assumes during and after creation."
        }
      ]
    },
    "Sources": {
      "allOf": [
        {
          "$ref": "#/components/schemas/__listOfInputSourceRequest"
        },
        {
          "xml": {
            "name": "sources"
          },
          "description": "The source URLs for a PULL-type input. Every PULL type input needs\nexactly two source URLs for redundancy.\nOnly specify sources for PULL type Inputs. Leave Destinations empty.\n"
        }
      ]
    },
    "Tags": {
      "allOf": [
        {
          "$ref": "#/components/schemas/Tags"
        },
        {
          "xml": {
            "name": "tags"
          },
          "description": "A collection of key-value pairs."
        }
      ]
    },
    "Type": {
      "allOf": [
        {
          "$ref": "#/components/schemas/InputType"
        },
        {
          "xml": {
            "name": "type"
          }
        }
      ]
    },
    "Vpc": {
      "allOf": [
        {
          "$ref": "#/components/schemas/InputVpcRequest"
        },
        {
          "xml": {
            "name": "vpc"
          }
        }
      ]
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/medialive-api-create-input-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.