Amazon Elastic Transcoder · Schema
CreateJobRequest
The CreateJobRequest structure.
Amazon Web ServicesMediaTranscodingVideo
Properties
| Name | Type | Description |
|---|---|---|
| PipelineId | object | |
| Input | object | |
| Inputs | object | |
| Output | object | |
| Outputs | object | |
| OutputKeyPrefix | object | |
| Playlists | object | |
| UserMetadata | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/amazon-elastic-transcoder/refs/heads/main/json-schema/amazon-elastic-transcoder-create-job-request-schema.json",
"title": "CreateJobRequest",
"description": "The <code>CreateJobRequest</code> structure.",
"type": "object",
"properties": {
"PipelineId": {
"allOf": [
{
"$ref": "#/components/schemas/Id"
},
{
"description": "The <code>Id</code> of the pipeline that you want Elastic Transcoder to use for transcoding. The pipeline determines several settings, including the Amazon S3 bucket from which Elastic Transcoder gets the files to transcode and the bucket into which Elastic Transcoder puts the transcoded files."
}
]
},
"Input": {
"allOf": [
{
"$ref": "#/components/schemas/JobInput"
},
{
"description": "A section of the request body that provides information about the file that is being transcoded."
}
]
},
"Inputs": {
"allOf": [
{
"$ref": "#/components/schemas/JobInputs"
},
{
"description": "A section of the request body that provides information about the files that are being transcoded."
}
]
},
"Output": {
"allOf": [
{
"$ref": "#/components/schemas/CreateJobOutput"
},
{
"description": " A section of the request body that provides information about the transcoded (target) file. We strongly recommend that you use the <code>Outputs</code> syntax instead of the <code>Output</code> syntax. "
}
]
},
"Outputs": {
"allOf": [
{
"$ref": "#/components/schemas/CreateJobOutputs"
},
{
"description": " A section of the request body that provides information about the transcoded (target) files. We recommend that you use the <code>Outputs</code> syntax instead of the <code>Output</code> syntax. "
}
]
},
"OutputKeyPrefix": {
"allOf": [
{
"$ref": "#/components/schemas/Key"
},
{
"description": "The value, if any, that you want Elastic Transcoder to prepend to the names of all files that this job creates, including output files, thumbnails, and playlists."
}
]
},
"Playlists": {
"allOf": [
{
"$ref": "#/components/schemas/CreateJobPlaylists"
},
{
"description": "<p>If you specify a preset in <code>PresetId</code> for which the value of <code>Container</code> is fmp4 (Fragmented MP4) or ts (MPEG-TS), Playlists contains information about the master playlists that you want Elastic Transcoder to create.</p> <p>The maximum number of master playlists in a job is 30.</p>"
}
]
},
"UserMetadata": {
"allOf": [
{
"$ref": "#/components/schemas/UserMetadata"
},
{
"description": "User-defined metadata that you want to associate with an Elastic Transcoder job. You specify metadata in <code>key/value</code> pairs, and you can add up to 10 <code>key/value</code> pairs per job. Elastic Transcoder does not guarantee that <code>key/value</code> pairs are returned in the same order in which you specify them."
}
]
}
},
"required": [
"PipelineId"
]
}
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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/amazon-elastic-transcoder-create-job-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.