Amazon Interactive Video Service

Name: Amazon Interactive Video Service API
Brand: Amazon Interactive Video Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaVideo Processinghmac28 EndpointsREST

For Agents

Provision live streaming channels, manage stream keys and recordings, and authorise playback for low-latency interactive video applications.

Quickstart

Get started with Amazon Interactive Video Service in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a low latency live streaming channel"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Interactive Video Service API.

Provision low-latency live streaming channels via /CreateChannel

Generate and rotate broadcast stream keys with /CreateStreamKey

Configure session recording to S3 through /CreateRecordingConfiguration

Authorise private playback via signed JWT with playback key pairs

GET STARTED

Start building with Amazon Interactive Video Service API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon Interactive Video Service, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon Interactive Video Service, keeping it validated and agent-ready. Amazon IVS is a managed live streaming service that ingests RTMPS broadcasts and delivers low-latency HLS playback to viewers worldwide. The 28-endpoint API covers channel creation, stream key rotation, recording configurations that archive sessions to S3, playback authorization keys for private streams, and EventBridge integration for real-time stream lifecycle signals. It is built for interactive applications such as live shopping, esports, and audience-driven shows where sub-five-second glass-to-glass latency matters.

Use Cases

Patterns agents use Amazon Interactive Video Service API for, with concrete tasks.

★ Live Shopping Streams

Power live shopping experiences where presenters demo products and viewers buy in real time. Amazon IVS provides sub-five-second latency, channel-per-creator provisioning, and EventBridge signals when streams start or stop so the storefront can flip product availability immediately. The /CreateChannel and /CreateStreamKey endpoints let teams onboard a new presenter in seconds rather than minutes.

Create a new IVS channel named 'spring-collection-live' with STANDARD type, generate a stream key, and return the ingest endpoint and playback URL

Creator Platform Channel Lifecycle

Run a creator economy platform where each user gets their own channel and stream key. The IVS API supports per-creator resource provisioning, stream key rotation when creators are compromised, and tag-based filtering so platform analytics can group streams by tier or vertical. Recording configurations let creators automatically archive every broadcast to S3 for VOD playback later.

Create a recording configuration that writes to bucket 'creator-archives' with thumbnail interval 60 and attach it to channel arn:aws:ivs:us-east-1:123:channel/abc

Private and Token-Gated Playback

Restrict live streams to authenticated viewers using IVS playback authorization. The /ImportPlaybackKeyPair endpoint imports an ECDSA public key, and the application backend signs short-lived JWTs that the player exchanges for stream access. This pattern fits paid events, internal town halls, and any context where playback URLs cannot be public.

Import a playback key pair named 'paid-event-key' with the supplied PEM public key for use signing playback JWTs

AI Agent Live Stream Operations

AI agents call Amazon IVS through Jentic to provision channels on demand, rotate compromised stream keys, and stop streams that violate policy. The agent searches Jentic for the right operation, loads the input schema, and executes with credentials kept in the Jentic vault. This is faster than embedding SigV4 signing into every agent runtime and keeps AWS keys out of the LLM context.

Search Jentic for 'stop a live stream', load the StopStream schema, and execute against channel arn:aws:ivs:us-east-1:123:channel/abc

Key Endpoints

28 endpoints — jentic publishes the only available openapi specification for amazon interactive video service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/CreateChannel

Create a live streaming channel

POST

/CreateStreamKey

Generate a broadcast stream key

POST

/CreateRecordingConfiguration

Configure S3 recording for a channel

POST

/ListStreams

List active live streams

POST

/StopStream

Stop an in-progress live stream

POST

/GetStream

Get details of a live stream session

POST

/BatchGetChannel

Batch fetch channel metadata

POST

/CreateChannel

Create a live streaming channel

POST

/CreateStreamKey

Generate a broadcast stream key

POST

/CreateRecordingConfiguration

Configure S3 recording for a channel

POST

/ListStreams

List active live streams

POST

/StopStream

Stop an in-progress live stream

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys for IVS are stored encrypted in the Jentic vault. Jentic performs SigV4 signing at execution time and returns scoped tokens to the agent, so raw AWS secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent such as 'create a live streaming channel' or 'stop a live stream' and Jentic returns the matching IVS operation with its input schema, so the agent can call the right endpoint without parsing AWS docs.

Time to first call

Direct AWS IVS integration: 1-2 days to wire up SigV4, IAM, and lifecycle handling. Through Jentic: under 1 hour — search, load the schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Elemental MediaPackage VOD

Package and deliver video-on-demand assets

Choose MediaPackage VOD when you need to repackage and deliver archived recordings to many playback formats after the live stream ends

Alternative

Kinesis Video Streams Archived Media

Retrieve archived video fragments from Kinesis Video Streams

Pick Kinesis Video Streams when ingesting from connected cameras and IoT devices rather than producer-driven RTMPS broadcasts

Complementary

AWS Elemental MediaTailor

Personalised ad insertion for video streams

Combine with IVS when you need server-side ad insertion into live or VOD streams

Complementary

AWS Elemental MediaStore

Low-latency storage optimised for media workflows

Use MediaStore for origin storage when delivering archived IVS content through CloudFront

FAQs

Specific to using Amazon Interactive Video Service API through Jentic.

Why is there no official OpenAPI spec for Amazon Interactive Video Service?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Interactive Video Service via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon IVS API use?

Amazon IVS uses AWS Signature Version 4 (SigV4) HMAC request signing. Each call must be signed with an access key, secret key, and optional session token scoped to the IVS IAM permissions. Through Jentic, these credentials sit in the encrypted vault and signing happens at execution time so the agent never sees the raw secret.

Can I create a private live stream with the Amazon IVS API?

Yes. Import an ECDSA public key with POST /ImportPlaybackKeyPair, then sign short-lived JWTs server-side with the matching private key. Configure the channel for authorized playback so the player must present a valid JWT to start playback.

What are the rate limits for the Amazon IVS API?

Per-region quotas apply, including limits on channels per account, concurrent live viewers, and TPS for control plane operations such as CreateChannel and CreateStreamKey. Check the IVS service quotas in the AWS console for the current limits in your account.

How do I provision a new creator channel through Jentic?

Search Jentic for 'create live streaming channel', load the schema for POST /CreateChannel, submit the channel name and type, then call POST /CreateStreamKey for the same channel ARN. Jentic handles SigV4 signing on both calls.

Can I record live streams to S3 using the Amazon IVS API?

Yes. POST /CreateRecordingConfiguration creates a configuration pointing at an S3 bucket with optional thumbnail intervals, and channels created or updated with that configuration ARN automatically archive every broadcast session to S3.

Can I stop a live stream remotely with the Amazon IVS API?

Yes. POST /StopStream takes a channel ARN and ends the active broadcast session. This is useful for moderation flows where the platform needs to terminate a stream that violates terms of service without waiting for the broadcaster to disconnect.