How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Bitmovin

Bitmovin Inputs API

The Inputs API from Bitmovin — 22 operation(s) for inputs.

Documentation Provider Profile APIs.io OpenAPI GitHub

Bitmovin Inputs API is one of 18 APIs that Bitmovin publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Inputs. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 22 operations across 22 paths, and defines 34 schemas. It is described by OpenAPI 3.0.1, at version 3.0.

Requests are made against a single base URL, https://api.bitmovin.com/v1.

22 operations 22 paths 34 schemas 18 DELETE4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
3.0
Base URL
https://api.bitmovin.com/v1
Authentication
API Key, API Key
Contact
Bitmovin Inc
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

Bitmovin Inputs API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Api-Key (ApiKeyAuth). An API key is passed in the header as X-Tenant-Org-Id (TenantOrgId). By default, every request must be authenticated.

  • ApiKeyAuth — Your Bitmovin API key
  • TenantOrgId — Your Bitmovin account organization

Paths & Operations 22

Across 22 paths, the API surfaces 22 operations — 18 DELETE, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Inputs 22
DELETE
/encoding/inputs/akamai-netstorage/{input_id}
Delete Akamai NetStorage Input
DeleteEncodingInputsAkamaiNetStorageByInputId 1 param → 200default
DELETE
/encoding/inputs/aspera/{input_id}
Delete Aspera Input
DeleteEncodingInputsAsperaByInputId 1 param → 200default
DELETE
/encoding/inputs/azure/{input_id}
Delete Azure Input
DeleteEncodingInputsAzureByInputId 1 param → 200default
DELETE
/encoding/inputs/direct-file-upload/{input_id}
Delete Direct File Upload Input
DeleteEncodingInputsDirectFileUploadByInputId 1 param → 200default
DELETE
/encoding/inputs/ftp/{input_id}
Delete FTP Input
DeleteEncodingInputsFtpByInputId 1 param → 200default
DELETE
/encoding/inputs/gcs/{input_id}
Delete GCS Input
DeleteEncodingInputsGcsByInputId 1 param → 200default
DELETE
/encoding/inputs/gcs-service-account/{input_id}
Delete Service Account based GCS Input
DeleteEncodingInputsGcsServiceAccountByInputId 1 param → 200default
DELETE
/encoding/inputs/generic-s3/{input_id}
Delete Generic S3 Input
DeleteEncodingInputsGenericS3ByInputId 1 param → 200default
DELETE
/encoding/inputs/hls/{input_id}
Delete HLS Input
DeleteEncodingInputsHLSByInputId 1 param → 200default
DELETE
/encoding/inputs/http/{input_id}
Delete HTTP Input
DeleteEncodingInputsHttpByInputId 1 param → 200default
DELETE
/encoding/inputs/https/{input_id}
Delete HTTPS Input
DeleteEncodingInputsHttpsByInputId 1 param → 200default
DELETE
/encoding/inputs/local/{input_id}
Delete Local Input
DeleteEncodingInputsLocalByInputId 1 param → 200default
DELETE
/encoding/inputs/redundant-rtmp/{input_id}
Delete Redundant RTMP Input
DeleteEncodingInputsRedundantRtmpById 1 param → 200default
DELETE
/encoding/inputs/s3/{input_id}
Delete S3 Input
DeleteEncodingInputsS3ByInputId 1 param → 200default
DELETE
/encoding/inputs/s3-role-based/{input_id}
Delete S3 Role-based Input
DeleteEncodingInputsS3RoleBasedByInputId 1 param → 200default
DELETE
/encoding/inputs/sftp/{input_id}
Delete SFTP Input
DeleteEncodingInputsSftpByInputId 1 param → 200default
DELETE
/encoding/inputs/srt/{input_id}
Delete SRT input
DeleteEncodingInputsSrtByInputId 1 param → 200default
DELETE
/encoding/inputs/zixi/{input_id}
Delete Zixi input
DeleteEncodingInputsZixiByInputId 1 param → 200default
POST
/encoding/inputs/s3-role-based
Create S3 Role-based Input
PostEncodingInputsS3RoleBased body → 201default
POST
/encoding/inputs/sftp
Create SFTP Input
PostEncodingInputsSftp body → 201default
POST
/encoding/inputs/srt
Create SRT input
PostEncodingInputsSrt body → 201default
POST
/encoding/inputs/zixi
Create Zixi input
PostEncodingInputsZixi body → 201default

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are ResponseErrorData (5 properties), ResponseEnvelope (4 properties), ResponseError (3 properties), Link (2 properties). Each schema is shown below with its type and property counts.

ResponseEnvelope
object
4 properties 3 required
AdMarkersSource
string
GenericS3Input
4 required
SrtInput
2 required
S3SignatureVersion
string
AzureServicePrincipal
object
Azure service principal credentials for Microsoft Entra ID authentication. This authentication method is usable from encoder version 2.273.0 onwards.
2 required
BitmovinResponse
object
1 property 1 required
FtpInput
1 required
AzureInput
2 required
GcsServiceAccountInput
2 required
S3RoleBasedInput
2 required
ResponseErrorData
object
5 properties 3 required
ExternalIdMode
string
BackupSrtInputs
object
2 properties 1 required
AwsCloudRegion
string
Message
2 required
MessageType
string
AkamaiNetStorageInput
3 required
ResultWrapper
object
1 property
HlsInput
GoogleCloudRegion
string
HttpInput
1 required
HttpsInput
1 required
Link
object
2 properties 1 required
Input
ResponseStatus
string
GcsInput
3 required
AsperaInput
1 required
S3AccessStyle
string
Specifies whether to use path or virtual-hosted style access
SftpInput
1 required
BitmovinResource
ResponseError
object
3 properties 3 required
SrtMode
string
ZixiInput

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bitmovin-inputs-api-openapi.yml Raw ↑

Other APIs Bitmovin publishes across the network.

Bitmovin Player API
AE Profile APIs.io
Bitmovin Analytics API
AE Profile APIs.io
Bitmovin Config API
AE Profile APIs.io
Bitmovin Configurations API
AE Profile APIs.io
Bitmovin Emails API
AE Profile APIs.io
Bitmovin Encodings API
AE Profile APIs.io
Bitmovin Filters API
AE Profile APIs.io
Bitmovin Infrastructure API
AE Profile APIs.io
Bitmovin Live API
AE Profile APIs.io
Bitmovin Manifests API
AE Profile APIs.io
Bitmovin Notifications API
AE Profile APIs.io
Bitmovin Outputs API
AE Profile APIs.io
#Inputs
← Back to B APIs
API Details
ID
bitmovin:bitmovin-inputs-api
Base URL
https://api.bitmovin.com/v1
Docs
https://developer.bitmovin.com/encoding/
Provider
Bitmovin
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=bitmovin-inputs-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/bitmovin-inputs-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Bitmovin Inputs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.