Wayline Data API

Programmatic access to game-industry data: the cross-platform join (a game's live Steam players, Twitch viewers, and price across every store, in one row), plus the full Steam and Unity Asset Store catalogs. One key, simple REST, JSON out.

Every key includes 1,000 calls per calendar month at no charge. Once you reach 1,000, further calls return an error (HTTP 429) until your allowance resets on the 1st of the next month (UTC). Paying to call past 1,000 isn't available yet.

Your API keys

Quick start

Authenticate every request with your key in an Authorization: Bearer header.

curl https://www.wayline.io/api/data/v1/unity/assets?q=tileset&limit=5 \
  -H "Authorization: Bearer YOUR_API_KEY"

Building an autonomous agent?

Agents are first-class here: one POST registers a named, revocable agent identity and returns a bearer secret, with no sign-in or browser step. Use that secret exactly like a key on every call.

curl -X POST https://www.wayline.io/api/data/v1/agents \
  -H "Content-Type: application/json" \
  -d '{"name":"my-agent","owner_email":"you@example.com"}'
# → { "secret": "wayline_agent_…", … }   (shown once; use it as the Bearer token)

Same free monthly allowance as a key. Revoke any time with DELETE /api/data/v1/agents using the agent's own secret. Full contract in the OpenAPI spec.

Prefer MCP? Connect a Model Context Protocol client to POST /api/data/v1/mcp (Streamable HTTP) to get these endpoints as typed tools, authenticated with the same secret.

The cross-platform join

The one view no single-platform source offers: a game's live Steam players, Twitch viewership, and price across stores, resolved into one row. Filter with q, has_steam, has_twitch.

Request

curl "https://www.wayline.io/api/data/v1/entities?has_twitch=true&limit=1" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response

{
  "data": [
    {
      "id": 16297,
      "name": "Fallout 4",
      "type": "game",
      "platforms": ["gog", "steam", "twitch"],
      "steam_ccu": 11506,
      "twitch_viewers": 13902,
      "prices": { "steam": 799, "gog": 1599 }
    }
  ],
  "total": 599,
  "pagination": { "limit": 1, "offset": 0 }
}

id Stable Wayline game id. Use it to correlate rows over time.

name Canonical game name (edition/version variants resolved together).

platforms Stores + platforms the game is present on (steam, twitch, gog, epic, nintendo, xbox, apple, google-play, itch).

steam_ccu Live Steam concurrent players. null if not currently sampled.

twitch_viewers Live Twitch viewers. null if not currently streamed.

prices Current price per store, in USD minor units (cents). Only stores that carry a price appear.

Endpoints

Beyond the catalog snapshot, the trending and history endpoints expose velocity: how fast a title is gaining reviews or ratings per day. We record every change our crawler observes as a timestamped event, so history is the real sequence of moves (not a fixed daily resample) and any window is exact. Recent-window velocity sharpens as the trail grows; where a window isn't available yet, trending returns a labelled fallback (Unity: lifetime ratings/day; Steam: total reviews).

GET /api/data/v1/entities Cross-platform games — live Steam players + Twitch viewers + price across stores, one row Params: q, has_steam, has_twitch, limit, offset

GET /api/data/v1/unity/publishers Unity Asset Store publishers Params: q, has_email, min_assets, limit, offset

GET /api/data/v1/unity/assets Unity Asset Store assets (ratings, pricing, category) Params: q, category, is_free, min_rating_count, limit, offset

GET /api/data/v1/steam/games Steam catalog (developers, genres, reviews, owners) Params: q, genre, is_indie, min_reviews, limit, offset

GET /api/data/v1/trending Top movers by review/rating velocity (gained per day) Params: source (steam|unity), window (days), limit, offset

GET /api/data/v1/steam/games/{appid}/history A Steam app’s review/price/ccu time-series + recent velocity Params: days

GET /api/data/v1/unity/assets/{id}/history A Unity asset’s rating/price time-series + recent velocity Params: days

GET /api/data/v1/catalog Wayline’s own asset catalog — published packs, atoms & products (title, price, engine) Params: category, engine, sort, page

GET /api/data/v1/usage Your usage this month Params: (none)

All list endpoints return { data: [...], pagination: { limit, offset, total } }. Page size defaults to 50, max 200.

Building against it with tooling or an AI agent? The full contract is published as a machine-readable OpenAPI 3.1 spec.