specification: API Commons Plans
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/Plans
provider: Yahoo
providerId: yahoo
created: '2026-05-04'
modified: '2026-08-28'
generated: '2026-08-28'
method: searched
source: >-
  https://sports.yahoo.com/developer , https://developer.yahoo.com/ ,
  https://help.yahooinc.com/dsp-api/docs/setup-access-guide ,
  https://help.yahooinc.com/datax/docs/security-authentication
tags:
  - Pricing
  - Plans
description: >-
  Yahoo publishes NO self-serve plans, tiers or per-call prices for any of its APIs. This file
  replaces a 2026-05-04 scaffold that invented Free / Professional / Enterprise tiers with
  fabricated quotas and TBD prices; none of those tiers exist. Access to every Yahoo API is
  granted by relationship, not purchase.
plans: []
plan_count: 0
access_model:
  - api: Yahoo Fantasy Sports API
    model: free-with-application
    detail: >-
      No charge and no published price. Developers register an app at
      developer.yahoo.com/apps/create/, agree to the API Access and Use Agreement, and apply for
      access at sports.yahoo.com/developer/access/. Yahoo reserves the right to throttle
      excessive use. There is no paid tier to upgrade to.
    source: https://sports.yahoo.com/developer
  - api: Yahoo DSP Traffic API
    model: customer-only
    detail: >-
      Available only to existing Yahoo DSP seat holders. A seat user must be created and
      API-enabled by a User Ops role holder in the DSP UI before client credentials can be
      generated. There is no public price list and no self-serve signup; cost is carried by the
      underlying DSP media contract.
    source: https://help.yahooinc.com/dsp-api/docs/setup-access-guide
  - api: Yahoo DSP Reporting API
    model: customer-only
    detail: Same seat-and-account-team gate as the Traffic API; no published price.
    source: https://help.yahooinc.com/dsp-api/docs/setup-access-guide
  - api: Yahoo Ad Tech DataX API
    model: partner-onboarding
    detail: >-
      Onboarding requires generating an RSA key pair and emailing the public key to
      dataoperations@yahooinc.com. Commercial terms are set per data partner; the API does expose
      a Fee resource for updating negotiated data fees, which confirms pricing is bilateral
      rather than published.
    source: https://help.yahooinc.com/datax/docs/security-authentication
  - api: Yahoo Conversion API
    model: customer-only
    detail: Requires a DSP pixel and a separate direct OAuth 2.0 setup; no published price.
    source: https://help.yahooinc.com/dsp-api/docs/yahoo-conversion-api
note: >-
  plan_count is a real, checked zero, not a gap in our research. Yahoo's developer surface is
  split between a free consumer API gated by an application form and a set of ad-tech APIs gated
  by an existing commercial relationship, and neither publishes a rate card.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com