Case 04 — 2026
Events app with a web UI and a REST API
A small Flask application for listing and filtering sports fixtures, with a JSON import path and an API alongside the pages. Built for the Sportradar Coding Academy.
Sports CalendarCourse projectWeb development
- API alongside the web UI
- REST
- Bulk import from external data
- JSON
- Route tests, not manual checks
- Tested
The
problem.
The exercise was deliberately narrow: show fixtures, let people filter them, allow new ones to be added. Narrow briefs are where structure shows — the temptation is one file, and the point is not to.
What we did
- Application factory pattern with routes, database access and templates separated, so the app can be configured per environment
- Filtering by sport and by date, plus a detail view per fixture
- Events accepted through both a form and a REST endpoint, sharing one validation path
- Bulk import from external JSON, with schema and seed data kept in version control
- Route tests covering the endpoints rather than a manual click-through
Stack
PythonFlaskSQLiteJinja2pytest
Same
story?
If any of this sounds like your business, the first call is free and the quote is fixed.
polistudio@polistudio.plPrefer Telegram? @polistudio