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

StreamElements songrequests API

Endpoints to interact with StreamElements Mediashare

StreamElements songrequests API is one of 24 APIs that StreamElements publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include songrequests. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 15 operations across 14 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.streamelements.com/kappa/v2, https://api.streamelements.com/kappa/v3.

15 operations 14 paths 22 schemas 1 DELETE12 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.streamelements.com/kappa/v2
Authentication
HTTP Bearer, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 3

StreamElements songrequests API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (JWTBearer). It accepts HTTP bearer tokens (ApiKeyBearer). It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 17 scopes. By default, every request must be authenticated.

Paths & Operations 15

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

songrequests 15

Endpoints to interact with StreamElements Mediashare

GET
/songrequest/playing
/playing
/playing 2 params → 200
GET
/songrequest/youtube
/youtube
/youtube 2 params → 200
GET
/songrequest/{channel}/settings
/:channel/settings
Get/:channel/settings 1 param → 200
GET
/songrequest/{channel}/settings/public
/:channel/settings/public
/:channel/settings/public 1 param → 200
GET
/songrequest/{channel}/queue
/:channel/queue
/:channel/queue 1 param → 200
POST
/songrequest/{channel}/queue
/:channel/queue
Post/:channel/queue 1 param body → 200404
DELETE
/songrequest/{channel}/queue/{song}
/:channel/queue/:song
/:channel/queue/:song 2 params → 201400
GET
/songrequest/{channel}/queue/public
/:channel/queue/public
/:channel/queue/public 1 param → 200
GET
/songrequest/{channel}/pending
/:channel/pending
/:channel/pending 1 param → 200
GET
/songrequest/{channel}/playlist
/:channel/playlist
/:channel/playlist 3 params → 200400
GET
/songrequest/{channel}/player
/:channel/player
/:channel/player 1 param → 200
POST
/songrequest/{channel}/player/{state}
/:channel/player/:state
/:channel/player/:state 3 params → 201400
GET
/songrequest/{channel}/history
/:channel/history
Get/:channel/history1 3 params → 200
GET
/songrequest/{channel}/playing
/:channel/playing
/:channel/playing 1 param → 200
GET
/songrequest/{channel}/next
/:channel/next
/:channel/next 1 param → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are MediaRequestData (11 properties), Song (10 properties), Bot1 (5 properties), Success48 (5 properties). Each schema is shown below with its type and property counts.

User2
object
2 properties 2 required
Statistics
object
3 properties 3 required
Detail
object
2 properties 2 required
Youtube
object
4 properties 1 required
MediaRequestData
object
11 properties 11 required
channel_redemptions_itemId
object
3 properties 3 required
Mediashare
object
2 properties 2 required
Tips
object
2 properties 2 required
Voteskip
object
2 properties 2 required
400-badrequest
object
4 properties 4 required
Song
object
10 properties 7 required
Users
object
2 properties 2 required
Bot1
object
5 properties 5 required
Success-searchbysongname
object
3 properties 3 required
Success53
object
1 property 1 required
channel_queuerequest
object
1 property 1 required
BackupPlaylist
object
2 properties 2 required
Player
object
1 property 1 required
MediaRequestQueue
object
4 properties 4 required
Video1
object
3 properties 3 required
Limits
object
3 properties 3 required
Success48
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

streamelements-songrequests-api-openapi.yml Raw ↑

Other APIs StreamElements publishes across the network.

StreamElements activities API
StreamElements bot API
StreamElements channels API
StreamElements chatstats API
StreamElements commands API
StreamElements contests API
StreamElements filters API
StreamElements giveaways API
StreamElements loyalties API
StreamElements modules API
StreamElements overlays API
StreamElements points API
Where this information came from

This is an independent, third-party profile of StreamElements songrequests 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.