API reference
One REST gateway fronts all products. Routes are namespaced by product slug and authorised by scoped keys, so a key issued for one app cannot read another app's data.
| Product | Base path | Scopes |
|---|---|---|
| SoccerPro | /v1/soccer | match, player, tactics |
| ArcheryPro | /v1/archery | scores, technique, workouts |
| SwimmingPro | /v1/swimming | strokes, splits, sessions |
| FitnessPro | /v1/fitness | workouts, body, nutrition |
| ShopPro | /v1/shop | products, orders |
| SmartFarming | /v1/farm | sensors, greenhouse, alerts |
SDK guides
🎯
Flutter / Dart
Used by every first-party app. shared_package carries the client.
🟨
JavaScript
For the web dashboards and landing surfaces.
🐍
Python
For analytics jobs and the Modbus ingest bridge.
Tutorials
- From Modbus register to dashboard — wiring a PLC to a live chart.
- Sensor-driven strike analytics — 1000 Hz sampling and what to do with it.
- Signed entitlements — how an app validates what a user may open.
- Deploying a product — build, host, and point the subdomain.
Build status. These docs ship with the platform landing while the
Browse the ecosystem →
docs. host is provisioned. The endpoint registry in
sihi_api is the authoritative source for live scopes.