dashboard

GET / is a LeetCode profile analyzer, not a JSON payload. Enter a username and the page loads the canonical routes on this origin.

Live:

• leetcode-stats.tashif.codes
• playground
• docs
• redoc

/playground is the route tester: substitute the handle, run one path or all of them, inspect latency and JSON. The SVG row has theme and exclude controls. Placeholder sample is demo. Use a real LeetCode username.

Input and output shapes: Envelope and schemas.

Recent handles sit in localStorage under a pg_recent_leetcode key. Clearing it only affects that browser.

flowchart TB
  UI[playground] --> S["GET /username summary"]
  UI --> P["GET /username/profile"]
  UI --> St["GET /username/stats"]
  UI --> Svg["GET /username/stats/svg"]
  UI --> C["GET /username/contests"]
  UI --> R["GET /username/rating"]
  UI --> H["GET /username/heatmap"]
  UI --> B["GET /username/badges"]

Nothing is proxied to a third party from the playground. The browser calls this FastAPI app. The app still hits LeetCode GraphQL server-side.