Stream Io Api Stream API

Name: Stream API
Brand: Stream API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey138 EndpointsREST

For Agents

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

Use for: I need to app settings, I want to app settings, Search for block list, Find all block lists

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

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

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Stream API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Stream API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fstream-io-api.com%2Fstream-io-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fstream-io-api.com%2Fstream-io-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Stream API.

Get App Settings

Update App Settings

Create block list

List block lists

Delete block list

Use Cases

Patterns agents use Stream API for, with concrete tasks.

GET STARTED

Start building with Stream API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

138 endpoints — stream-io-api.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Stream API through Jentic.

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.

Stream Io Api Stream API

Connect the Stream API to your agent

Capabilities

Use Cases

Start building with Stream API

Key Endpoints

Why Jentic?

Related APIs

FAQs