Developer Hub

A small, predictable REST API for research workflows. Every successful response includes a data-basis block so software and agents can distinguish observations from estimates.

Manage API keys

First request

API access is available to Advanced and Premium members. Create a key in Settings and send it only from server-side code.

1
Create a key
Copy it once; only its hash is stored.
2
Add Bearer auth
Never expose the key in browser JavaScript.
3
Read basis first
Check crawl time and whether history is observed.

curl --request GET \
  --url "https://school.djai.academy/api/game-analytics/v1/movers?limit=10" \
  --header "Authorization: Bearer $DJAI_GAME_ANALYTICS_KEY"

Data contract

What downstream code can safely assume.

Install buckets are Google Play lower bounds, not exact downloads.
Estimated installs/day is modeled from observed rating movement.
History is built from DJAI crawls; the API does not fabricate earlier dates.
Quota is charged only after a successful endpoint result.

Endpoints

Base path: /api/game-analytics/v1

OpenAPI JSON

Method	Path	Purpose
GET	/overview	Market totals and current crawl freshness
GET	/movers	Ranked games with optional category, age, and rating filters
GET	/new-releases	Recently released games inside a chosen time window
GET	/genres	Current genre rollups and monetization mix
GET	/search?q=...	Search tracked games by title or developer
GET	/games/{appId}	One tracked app and its current metrics
GET	/games/{appId}/history?days=90	Observed snapshot and chart-rank history
GET	/compare?appIds=id1,id2	Compare two or more tracked apps

Understand every metric

Read sources, limitations, traction-v1, momentum, and history semantics.

Read methodology

Keys and usage

Create or revoke a key and review the limits tied to your School membership.

Open settings