canonical: https://jentic.com/apis/stream-io-api.com/stream-io-api

# Stream Io Api Stream API

stream-io-api.com/main version v166.1.0. The API exposes 138 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get app settings, update app settings. Covers 138 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Get App Settings
- Update App Settings
- Create block list
- List block lists
- Delete block list

## Use cases

### Media and Content Operations

Use the Stream API to perform media operations programmatically. The API provides 138 endpoints covering core functionality including get app settings, update app settings, create block list.

Example prompt: Call GET /app to get app settings

### Automated App Management

Automate app operations by combining multiple Stream API endpoints. Agents can update app settings and then create block list in a single workflow.

Example prompt: Call PATCH /app to update app settings, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Stream API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get app settings', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/app` | Get App Settings |
| PATCH | `/app` | Update App Settings |
| POST | `/blocklists` | Create block list |
| GET | `/blocklists` | List block lists |
| GET | `/blocklists/{name}` | Get block list |
| PUT | `/blocklists/{name}` | Update block list |
| DELETE | `/blocklists/{name}` | Delete block list |
| GET | `/campaigns/{id}` | Get campaign |

## Key resources

- **App** — Operations for app
- **Blocklists** — Operations for blocklists
- **Campaigns** — Operations for campaigns
- **Channels** — Operations for channels
- **Channeltypes** — Operations for channeltypes

## Why Jentic

- **Setup:** Wiring the Stream API by hand means generating server-side JWTs, attaching your application api_key on every query, and setting the stream-auth-type header correctly yourself. Through Jentic you install once, import the Stream API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Stream puts the resource name in the URL path (`/blocklists/{name}`, `/campaigns/{id}`), so a rule can pin your agent to a single blocklist or campaign: it reads and updates that one and nothing else. You choose the operations it may call, so destructive ones like deleting a blocklist are not included unless you add them.
- **Credential handling:** Your Stream API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get app settings' or 'create a blocklist', and Jentic returns the matching Stream operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the Stream API use?

The Stream API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get app settings with the Stream API?

Yes. Use the GET /app endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Stream API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get app settings through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get app settings'. Jentic returns the matching Stream API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Stream API have?

The Stream API exposes 138 endpoints covering app, blocklists, campaigns operations.

### Can I limit what my agent is allowed to do with the Stream API?

Yes. Because you run Jentic One yourself, your own rules decide which Stream API operations and credentials the agent may use. Since Stream puts the resource name in the URL path, such as `/blocklists/{name}` and `/campaigns/{id}`, a rule can pin the agent to a single blocklist or campaign so it only reads and updates that one and nothing else. You also choose which operations it may call, so a destructive request like DELETE `/blocklists/{name}` stays unavailable unless you add it.