Skip to main content
The 8bitedge API gives retro game sellers and integrators programmatic access to the market intelligence they need to compete. Whether you’re running a storefront, a pricing tool, or an inventory management system, 8bitedge surfaces what buyers are actually searching for, which titles are trending, what condition they want, and what those games are worth — all in a single, consistent REST interface. Instead of guessing what to stock, you can let real buyer behavior drive your decisions.

What problem does 8bitedge solve?

Retro game retail moves fast. A title that sat on a shelf for months can spike overnight after a YouTube video, a speedrunning event, or a new port announcement. Without a signal layer, sellers are flying blind — relying on gut feel, stale price guides, or manual eBay research. 8bitedge solves this by turning buyer intent data (search clicks, watchlist behavior, search volume, condition preferences) into structured, queryable intelligence you can act on programmatically. The API answers three questions in real time:
  • What do buyers want? The demand leaderboards rank games and consoles by intent, watches, and momentum across day, 7-day, and 30-day windows.
  • Which titles are trending? Momentum scores compare a title’s recent pace against its 30-day baseline, flagging rising, steady, or cooling games before the market moves.
  • What condition are buyers seeking? Condition signals break down buyer preferences (loose, CIB, new) at both the individual game level and market-wide, so you price and source with precision.

Resource areas

The API is organized into four main areas:
AreaDescriptionStatus
GamesFull catalog metadata — names, slugs, pricing (loose/complete/new) — for every enabled game in the catalogLive
ConsolesEnabled console catalog with ids and display namesLive
Demand & IntentSeller-facing demand metrics: leaderboards, momentum, condition signals, search analyticsLive

Get started

Quickstart

Make your first authenticated call and pull a demand leaderboard in five minutes.

Authentication

Understand bearer API keys, scopes, and how to handle auth errors.

Demand Signals Guide

Learn how to read momentum scores, condition breakdowns, and search analytics.

Account Endpoint

Inspect your organization, plan limits, and current usage with GET /api/v1/me.

Games API

Browse and search the full game catalog by id, slug, title, or console.

Consoles API

Paginated list of all enabled consoles with ids and display names.

Demand Games

Leaderboard and profiles for game-level demand, momentum, and pricing signals.

Demand Searches

Popular-search leaderboard, trending queries, and unmet-demand (supply gap) data.

Demand Conditions

Condition breakdown (loose, CIB, new) for individual games and market-wide mix.

Batch Requests

Submit multiple items in one POST for the Intelligence, Signals, and Enrichment categories.

Key capabilities

Demand Leaderboards

Rank games and consoles by intent (redirect clicks + distinct-user reach), sortable by intent, watches, or momentum across day, 7d, and 30d windows.

Condition Signals

See the exact condition breakdown buyers prefer for any individual game — loose, CIB, or new — so you source and price to match real demand.

Search Analytics

Query the popular-search leaderboard, identify unmet demand (high-volume searches with little inventory), and track rising search terms.

Game Catalog

Look up games by id, slug, or display title. Fetch every title for a console. All results include loose, complete, and new pricing.

Console Catalog

Paginated list of all enabled consoles with ids and display names, ready to use as foreign keys against game and demand data.

Batch Requests

Submit multiple items in a single POST for Intelligence, Signals, and Enrichment categories. Each item is independently metered; mixed success returns a 207 per-item envelope.

Versioning

All endpoints are served under the /api/v1 path prefix. The version is carried in the URL rather than a header, so your integration targets an explicit contract. Future breaking changes will be introduced under a new prefix (e.g. /api/v2) — existing /api/v1 consumers will not be affected until they choose to migrate.
The base URL for all requests is https://api.8bitedge.com. Every endpoint in this documentation is shown as a path relative to that base, e.g. GET /api/v1/me.