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

This API Reference uses a hybrid model:
  • OpenAPI endpoints for broad, generated route coverage.
  • Domain API guides for workflow notes, caveats, and implementation context by backend domain.
Use the API Fundamentals section for authentication and error handling guidance, the Domain API Guides section for integration context, and the Endpoints section for generated request/response reference from api-reference/openapi.json.

​
Domain guides

​
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.