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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Roku

Roku devices API

The devices API from Roku — 6 operation(s) for devices.

Documentation Provider Profile APIs.io OpenAPI GitHub

Roku devices API is one of 27 APIs that Roku publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 20 JSON Schema definitions.

Tagged areas include Devices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a JSON-LD context, and 20 JSON Schemas.

This API exposes 9 operations across 6 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.3.29.

Requests are made against a single base URL, https://api.cloud.roku.dev.

9 operations 6 paths 12 schemas 1 DELETE4 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.3.29
Server
https://api.cloud.roku.dev
Contact
DevX Tools Team
Resource Areas
1

Paths & Operations 9

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

devices 9
GET
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices
Roku List Devices
devices-list_devices 12 params → 200422
POST
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices
Roku Create Device
devices-create_device 2 params body → 201422
GET
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices/{device_id}
Roku Get Device
devices-get_device 3 params → 200422
PATCH
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices/{device_id}
Roku Update Device
devices-update_device 3 params body → 200422
DELETE
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices/{device_id}
Roku Delete Device
devices-delete_device 4 params → 204422
POST
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices/{device_id}/start
Roku Start Device
devices-start_device 4 params body → 202422
POST
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices/{device_id}/stop
Roku Stop Device
devices-stop_device 3 params → 202422
GET
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices/{device_id}/runs
Roku Get Device Runs
devices-get_device_runs 3 params → 200422
GET
/api/v1/organisations/{organisation_id}/projects/{project_id}/devices/{device_id}/logs/{instance_id}
Roku Read Logs
devices-read_logs 4 params → 200422

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are DeviceInstanceInfo (21 properties), DeviceHistoryOut (17 properties), DeviceOut (14 properties), DeviceStart (7 properties). Each schema is shown below with its type and property counts.

DeviceInstanceInfo
object
21 properties 10 required
IceServer
object
3 properties 1 required
DeviceHistoryOut
object
17 properties 12 required
ValidationError
object
3 properties 3 required
DeviceUpdate
object
5 properties
KubernetesStatus
string
DeviceOut
object
14 properties 5 required
HTTPValidationError
object
1 property
DeviceStart
object
7 properties 4 required
DeviceType
string
DeviceCreate
object
6 properties 2 required
DeviceStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

roku-devices-api-openapi.yml Raw ↑

Other APIs Roku publishes across the network.

Roku BrightScript SDK
AE Profile APIs.io
Roku SceneGraph
AE Profile APIs.io
Roku Search Feed
AE Profile APIs.io
Roku Direct Publisher Feed
AE Profile APIs.io
Roku Analytics
AE Profile APIs.io
Roku Authentication Framework
AE Profile APIs.io
Roku Apps API
AE Profile APIs.io
Roku asyncapi API
AE Profile APIs.io
Roku Billing API
AE Profile APIs.io
Roku builds API
AE Profile APIs.io
Roku Diagnostics API
AE Profile APIs.io
Roku Discovery API
AE Profile APIs.io
#Devices
← Back to R APIs
API Details
ID
roku:roku-devices-api
Server
https://api.cloud.roku.dev
Docs
https://developer.roku.com/docs/references/brightscript/component-reference.md
Provider
Roku
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=roku-devices-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/roku-devices-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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