API archive entry · source-reported

Amazon Interactive Video Service

Introduction The Amazon Interactive Video Service (IVS) API is REST compatible, using a standard HTTP API and an Amazon Web Services EventBridge event stream for responses. JSON is used for both requests and responses, including errors. The API is an Amazon Web Services regional service. For a list of supported regions and Amazon IVS HTTPS service endpoints, see the Amazon IVS page in the Amazon Web Services General Reference . All API request parameters and URLs are case sensitive. For a summary of notable documentation changes in each release, see Document History . Allowed Header Values Accept: application/json Accept-Encoding: gzip, deflate Content-Type: application/json Resources The following resources contain information about your IVS live stream (see Getting Started with Amazon IVS ): Channel — Stores configuration data related to your live stream. You first create a channel and then use the channel’s stream key to start your live stream. See the Channel endpoints for more information. Stream key — An identifier assigned by Amazon IVS when you create a channel, which is then used to authorize streaming. See the StreamKey endpoints for more information. Treat the stream key

Provider / source website

Documentation & source

Use the provider’s reference for current endpoints, setup, limits and terms.

No separate documentation URL has been confirmed for this record.

Open provider / source ↗

Provider content retains its own terms. This listing does not grant reuse or training rights.

Where these facts came from

AltAPIs imported it from APIs.guru OpenAPI Directory. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Sep 20, 2026
  2. Last directory-field change: Sep 20, 2026
  3. Current source observation: Sep 20, 2026

Submit a source-backed correction

Source reference

APIs.guru OpenAPI Directory

This page separates source-reported facts from questions that need live provider verification.