A small FastAPI microservice that fetches hockey schedules from stats.swehockey.se, parses the raw HTML, and exposes a clean JSON API for a specific team. Primarily designed to run as a Kubernetes pod so Glance dashboard instances can reach it via internal cluster DNS:

- type: custom-api
  title: Hockey – Matches
  cache: 30m
  url: http://hockey-api:8000/team

The API supports any team, based on a configurable substring (e.g., "modo", "aik", "björklöven"). No code changes are required — everything is configured via environment variables.

• Fetches & parses games from one or more Swehockey schedule URLs

• Supports any team through a simple environment variable (TEAM_TAG)

• Returns both last played game and next upcoming game

• Automatically fetches team badges/logos from TheSportsDB

• Computes match result from your team’s perspective:

  • "win", "loss", "draw"

• Lightweight, fast, cache-friendly

• Perfect for use with Glance dashboards, Home Assistant, or custom UIs

• Stateless → easy to deploy in Docker, Kubernetes, or k3s

Run the API for MoDo Hockey:

docker run -d \
  -p 8000:8000 \
  -e TEAM_TAG="modo" \
  -e SCHEDULE_URLS="https://stats.swehockey.se/ScheduleAndResults/Schedule/18266,https://stats.swehockey.se/ScheduleAndResults/Schedule/18267" \
  -e THESPORTSDB_API_KEY="YOUR_API_KEY" \
  hockey-api:latest

Then open:

http://localhost:8000/team

The service is configured entirely with environment variables:

The API matches all games where TEAM_TAG appears in either team name. Examples:

Returns the last played match and the next upcoming match for TEAM_TAG.

{
  "team_tag": "modo",
  "team_name": "MoDo Hockey",
  "schedule_urls": [
    "https://stats.swehockey.se/ScheduleAndResults/Schedule/18266",
    "https://stats.swehockey.se/ScheduleAndResults/Schedule/18267"
  ],
  "last_game": {
    "date": "2025-11-26",
    "time": "19:00",
    "home_team": "AIK",
    "away_team": "MoDo Hockey",
    "home_score": 1,
    "away_score": 2,
    "venue": "Hovet, Johanneshov",
    "round_detail": "",
    "home_badge": "https://r2.thesportsdb.com/images/media/team/badge123.png",
    "away_badge": "https://r2.thesportsdb.com/images/media/team/badge456.png",
    "team_result": "win"
  },
  "next_game": {
    "date": "2025-11-28",
    "time": "20:30",
    "home_team": "MoDo Hockey",
    "away_team": "IF Björklöven",
    "home_score": null,
    "away_score": null,
    "venue": "Hägglunds Arena",
    "round_detail": "Kvartsfinal 2",
    "home_badge": "...",
    "away_badge": "..."
  }
}

services:
  hockey-api:
    image: hockey-api:latest
    environment:
      TEAM_TAG: "MoDo"
      SCHEDULE_URLS: "https://stats.swehockey.se/ScheduleAndResults/Schedule/18266,https://stats.swehockey.se/ScheduleAndResults/Schedule/18267"
      THESPORTSDB_API_KEY: "YOUR_API_KEY"
    ports:
      - "8000:8000"

The Docker image is built and pushed automatically to GHCR via GitHub Actions when a version tag is pushed:

git tag v1.x.x
git push --tags

Once the Action completes, update the image tag in your k8s manifest and apply it manually on your cluster.

Save as k8s/hockey-api.yaml:

apiVersion: v1
kind: Namespace
metadata:
  name: hockey
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: hockey-api-config
  namespace: hockey
data:
  TEAM_TAG: "modo"
  SCHEDULE_URLS: "https://stats.swehockey.se/ScheduleAndResults/Schedule/18266,https://stats.swehockey.se/ScheduleAndResults/Schedule/18267"
---
apiVersion: v1
kind: Secret
metadata:
  name: hockey-api-secret
  namespace: hockey
type: Opaque
stringData:
  THESPORTSDB_API_KEY: "YOUR_API_KEY"
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: hockey-api
  namespace: hockey
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hockey-api
  template:
    metadata:
      labels:
        app: hockey-api
    spec:
      containers:
        - name: hockey-api
          image: <registry>/hockey-api:latest
          imagePullPolicy: Always
          ports:
            - containerPort: 8000
          envFrom:
            - configMapRef:
                name: hockey-api-config
            - secretRef:
                name: hockey-api-secret
          readinessProbe:
            httpGet:
              path: /
              port: 8000
            initialDelaySeconds: 5
            periodSeconds: 10
          livenessProbe:
            httpGet:
              path: /
              port: 8000
            initialDelaySeconds: 15
            periodSeconds: 20
---
apiVersion: v1
kind: Service
metadata:
  name: hockey-api
  namespace: hockey
spec:
  selector:
    app: hockey-api
  ports:
    - name: http
      port: 8000
      targetPort: 8000
  type: ClusterIP

kubectl apply -f k8s/hockey-api.yaml
kubectl -n hockey rollout status deploy/hockey-api
kubectl -n hockey get pods,svc

kubectl -n hockey port-forward svc/hockey-api 8000:8000
curl http://localhost:8000/team

If you run an ingress controller (nginx/traefik), add an Ingress resource for hockey-api on port 8000.

Here is a minimal Glance widget example:

- type: custom-api
  title: Hockey – Matches
  cache: 30m
  url: http://hockey-api:8000/team

You can customize it with logos, score colors, etc.

Make code changes locally, then push a version tag to GitHub to trigger a build:

git tag v1.x.x
git push --tags

GitHub Actions will build and push the Docker image to GHCR. From there, update the image tag in your k8s manifest and apply it manually on your cluster to test.

1. Fetches Swehockey schedule HTML

2. Extracts text and splits it into logical lines

3. Parses:

   • Dates
   • Times
   • Teams
   • Results (if available)
   • Spectators
   • Venue

4. Filters by your TEAM_TAG

5. Computes last/next games

6. Fetches badges via TheSportsDB

7. Returns clean JSON suited for dashboards

Pull requests and issues are welcome! Ideas for improvements include:

• better parser for irregular Swehockey formats
• multi-team support (/team/{tag})
• caching layer
• tests
• logo provider fallbacks
• automatic schedule discovery

MIT License – you are free to use, modify and distribute.