Skip to main content

​
D-Sports API

The primary API and backend for the D-Sports platform is d-sports-api (the PWA). It serves the web app, the native app (d-sports-engage-native), and is used by the marketing site (d-sports-site) where needed. Authentication, quests, leaderboards, collectibles, shop, and wallet flows all go through this API. Mic’d Up (d-sports-mic-d-up) has its own backend (Express + PostgreSQL) for live audio rooms and does not use the d-sports-api backend.

​
How this reference is built

D-Sports Docs can show API reference in two ways:
  • OpenAPI — Add an OpenAPI spec (e.g. from d-sports-api) to docs.json or link to it; Mintlify generates interactive playground and docs from it.
  • MDX — Write endpoint pages manually with the openapi or api frontmatter field for small APIs or custom docs.
The Endpoint examples in the sidebar are real d-sports-api endpoints. They use the OpenAPI spec in api-reference/openapi.json, which documents leaderboard, teams, packs, locker room, follow, and RevenueCat webhook endpoints. For the full API surface and source, see the d-sports-api repo.

​
Authentication

d-sports-api uses Clerk for authentication. API requests that require a user typically use Bearer tokens or session-based auth as configured in the app. Exact auth scheme (e.g. bearerAuth) is defined in the OpenAPI spec when one is published.

d-sports-api

Backend and PWA: stack, features, and how to run it.

Mic'd Up backend

Separate backend for live audio rooms.