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 Billing API

Billing cycle and credit management

Roku Billing 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 Billing. 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 3 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://apipub.roku.com/listen/transaction-service.svc.

3 operations 3 paths 5 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Server
https://apipub.roku.com/listen/transaction-service.svc
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Roku Billing API declares 1 security scheme for authenticating requests. An API key is passed in the query as partnerAPIKey (PartnerAPIKey). By default, every request must be authenticated.

  • PartnerAPIKey — Roku-issued Partner API Key. For GET endpoints the key is included in the URL path; for POST endpoints it is included in the request body. Channels obtain this…

Paths & Operations 3

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

Billing 3

Billing cycle and credit management

POST
/refund-subscription
Roku Refund Subscription
refundSubscription body → 200400401
POST
/update-bill-cycle
Roku Update Bill Cycle
updateBillCycle body → 200400401
POST
/issue-service-credit
Roku Issue Service Credit
issueServiceCredit body → 200400401

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are SubscriptionResult (6 properties), RefundSubscriptionRequest (6 properties), UpdateBillCycleRequest (5 properties), IssueCreditRequest (5 properties). Each schema is shown below with its type and property counts.

RefundSubscriptionRequest
object
6 properties 3 required
Error
object
3 properties
IssueCreditRequest
object
5 properties 4 required
SubscriptionResult
object
6 properties
UpdateBillCycleRequest
object
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

roku-billing-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 builds API
Roku devices API
Roku Diagnostics API
Roku Discovery API
Where this information came from

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