specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Twitch
providerId: twitch
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: true
tags:
  - Streaming
  - Developer API
  - Free
  - FinOps
  - FOCUS
description: FOCUS-aligned FinOps for the Twitch developer surface — the Helix and Extensions APIs are
  free of charge under Twitch's developer terms, so the FinOps surface is governance-focused (rate-limit
  budgets and bucket consumption) rather than dollar-cost. There is no metered invoice line; cost lives
  in the indirect engineering and infrastructure cost of operating against Twitch's APIs.
sources:
  - https://dev.twitch.tv/docs/api/
  - https://dev.twitch.tv/docs/api/guide/
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
publisherName: Twitch Interactive, Inc.
serviceCategory: Streaming Developer API
billingModel:
  pricingCategory: Free
  billingFrequency: On-Demand
  billingCurrency: USD
  chargeCategories:
    - Usage
focusColumns:
  ServiceName: Twitch Helix API
  ServiceCategory: Streaming Developer API
  ProviderName: Twitch
  PublisherName: Twitch Interactive, Inc.
  InvoiceIssuerName: Twitch Interactive, Inc.
  BillingCurrency: USD
meters:
  - name: helix_requests
    description: Helix API requests issued by your registered application; consumes points from the relevant
      bucket.
    unit: request
    aggregation: sum
    dimensions:
      - client_id
      - token_type
      - endpoint
  - name: bucket_points
    description: Points deducted from the token bucket; the practical FinOps unit since Twitch does not
      charge in dollars.
    unit: point
    aggregation: sum
    dimensions:
      - client_id
      - token_type
  - name: eventsub_subscriptions
    description: Active EventSub webhook subscriptions on the application.
    unit: subscription
    aggregation: max
    dimensions:
      - client_id
principles:
  - name: Visibility
    description: Use the Ratelimit-Limit / Remaining / Reset response headers and per-application logging
      to track point consumption across app and user buckets in real time.
  - name: Allocation
    description: Allocate "cost" to the consuming feature by tagging requests with the originating internal
      service or feature flag; bucket headroom is the budget being allocated.
  - name: Optimization
    description: Cache responses, prefer EventSub webhooks over polling, batch lookups (e.g. bulk Get
      Users), and use app tokens for non-user-scoped reads to avoid per-user bucket pressure.
  - name: Accountability
    description: Assign a developer owner per Twitch application (client ID); they are responsible for
      respecting the bucket, handling 429s with backoff, and migrating away from deprecated endpoints.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com