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

Roku personal-access-tokens API

The personal-access-tokens API from Roku — 4 operation(s) for personal-access-tokens.

Roku personal-access-tokens 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 Personal Access Tokens. 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 5 operations across 4 paths, and defines 8 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.

5 operations 4 paths 8 schemas 1 DELETE2 GET1 PATCH1 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
Resource Areas
1

Paths & Operations 5

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

personal-access-tokens 5
GET
/api/v1/users/me/personal_access_tokens
Roku List Personal Access Tokens
personal-access-tokens-list_personal_access_tokens → 200
POST
/api/v1/users/me/personal_access_tokens
Roku Create Personal Access Token
personal-access-tokens-create_personal_access_token body → 200422
DELETE
/api/v1/users/me/personal_access_tokens/{token_id}
Roku Revoke Personal Access Token
personal-access-tokens-revoke_personal_access_token 1 param → 200422
GET
/api/v1/users/me/personal_access_tokens/scopes
Roku Get Personal Access Token Scopes
personal-access-tokens-get_personal_access_token_scopes → 200
PATCH
/api/v1/users/me/personal_access_tokens/{token_id}/refresh
Roku Refresh Personal Access Token
personal-access-tokens-refresh_personal_access_token 1 param body → 200422

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are PersonalAccessTokenOut (10 properties), PersonalAccessTokenCreate (4 properties), ValidationError (3 properties), ScopeOut (3 properties). Each schema is shown below with its type and property counts.

PersonalAccessTokenStatus
string
PersonalAccessTokenRefresh
object
1 property
ScopeOut
object
3 properties 3 required
ValidationError
object
3 properties 3 required
PersonalAccessTokenCreate
object
4 properties 2 required
PersonalAccessTokenCreated
object
Response when a new PAT is created - includes the actual token
2 properties 2 required
HTTPValidationError
object
1 property
PersonalAccessTokenOut
object
10 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

roku-personal-access-tokens-api-openapi.yml Raw ↑

Other APIs Roku publishes across the network.

Roku BrightScript SDK
Roku SceneGraph
Roku Search Feed
Roku Direct Publisher Feed
Roku Analytics
Roku Authentication Framework
Roku Apps API
Roku asyncapi API
Roku Billing API
Roku builds API
Roku devices API
Roku Diagnostics API
Where this information came from

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