specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: TikTok
providerId: tiktok
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:
  - Social
  - Video
  - FinOps
  - FOCUS
description: 'FOCUS-aligned FinOps for the TikTok developer APIs: free, approval-gated access with no
  per-call billing. FinOps focus is on quota burn and approval-tier entitlements rather than cost.'
sources:
  - https://developers.tiktok.com/products
  - https://developers.tiktok.com/doc/tiktok-api-v2-rate-limit
  - https://focus.finops.org/focus-specification/v1-3/
notes: TikTok does not bill developers per call. There is no usage-based invoice surface; FinOps observability
  is limited to internal telemetry against the published 600 rpm per-endpoint limits.
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: TikTok Pte. Ltd.
serviceCategory: Social Platform APIs
billingModel:
  pricingCategory: Free / Approval-Gated
  billingFrequency: N/A
  billingCurrency: USD
  chargeCategories:
    - Usage
focusColumns:
  ServiceName: TikTok Developer Platform
  ServiceCategory: Social Platform APIs
  ProviderName: TikTok
  PublisherName: TikTok Pte. Ltd.
  BillingCurrency: USD
  ChargeCategory: Usage
meters:
  - name: user_info_requests
    unit: request
    aggregation: sum
    dimensions:
      - client_key
      - endpoint
  - name: video_query_requests
    unit: request
    aggregation: sum
    dimensions:
      - client_key
      - endpoint
  - name: video_list_requests
    unit: request
    aggregation: sum
    dimensions:
      - client_key
      - endpoint
principles:
  - name: Visibility
    description: Track per-client_key request volume against the 600 rpm sliding window for /v2/user/info,
      /v2/video/query, and /v2/video/list to anticipate 429s.
  - name: Allocation
    description: Issue distinct client keys per app so quota burn and approval-tier entitlements (Research,
      Commercial Content) can be attributed to the consuming product team.
  - name: Optimization
    description: Cache user_info responses, batch video queries, and avoid redundant list polls; request
      a quota raise via TikTok Support before redesigning around the limit.
  - name: Accountability
    description: Designate a developer-relations owner accountable for the TikTok app review status,
      approval-tier renewals, and Support tickets for limit increases.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com