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

overshoot.ai Streams API

Create, inspect, keep alive, and delete live video streams.

overshoot.ai Streams API is one of 8 APIs that overshoot.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Streams. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

This API exposes 4 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 0.4.0.

Requests are made against a single base URL, https://api.overshoot.ai/v1beta.

4 operations 3 paths 7 schemas 1 DELETE1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.4.0
Base URL
https://api.overshoot.ai/v1beta
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

overshoot.ai Streams API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API_Key).

  • API_Key — Bearer

Paths & Operations 4

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

Streams 4

Create, inspect, keep alive, and delete live video streams.

POST
/streams
Create stream
createStream 1 param → 201401403409503
GET
/streams/{stream_id}
Get stream
getStream 2 params → 200401404409
DELETE
/streams/{stream_id}
Delete stream
deleteStream 2 params → 200401404409
POST
/streams/{stream_id}/keepalive
Renew stream lease
keepaliveStream 2 params → 200401404409

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are StreamStatusResponse (17 properties), CreateStreamResponse (5 properties), KeepaliveResponse (5 properties), PublishInfo (3 properties). Each schema is shown below with its type and property counts.

Error
object
Standard error body used by stream-lifecycle and billing endpoints.
1 property 1 required
KeepaliveResponse
object
5 properties 4 required
RegionError
object
Returned on 409 when the request reaches the wrong region.
1 property
CreateStreamResponse
object
5 properties 5 required
PublishInfo
object
WebRTC publish target. Connect with the LiveKit client SDK.
3 properties 3 required
StreamStatusResponse
object
17 properties 2 required
DeleteStreamResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

overshootai-streams-api-openapi.yml Raw ↑

Other APIs overshoot.ai publishes across the network.

overshoot.ai Billing API
overshoot.ai Chat API
overshoot.ai Healthz API
overshoot.ai Metrics API
overshoot.ai Models API
overshoot.ai Readyz API
overshoot.ai V1beta API
Where this information came from

This is an independent, third-party profile of overshoot.ai Streams 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.