Endpoint reference
| Method | Route | Auth | Purpose |
|---|---|---|---|
GET | /matches | User | List matches with filters |
GET | /matches/live | User | All currently live matches |
POST | /user/follow/match | User | Follow a match |
PATCH | /user/follow/match/:id/team | User | Change supported team |
DELETE | /user/follow/match/:id | User | Unfollow a match |
GET | /admin/sportmonks/fixtures | Admin | Fetch fixtures from SportMonks |
POST | /admin/cache/clear | Admin | Clear cached match data |
GET | /admin/cache/stats | Admin | View cache statistics |
List matches
GET /matches User
List matches with optional filters. Returns paginated results.
Filter by league ID.
Filter by match status. Values:
upcoming, live, completed.ISO 8601 date string. Only return matches starting after this date.
ISO 8601 date string. Only return matches starting before this date.
- Request
- Response
GET /matches/live User
Returns all currently live matches across all leagues. No query parameters.
Match following
These endpoints manage which matches a user follows. Following a match enables push notifications and Live Activity updates.See the Match following business flow for the full end-to-end journey.
POST /user/follow/match User
Follow a match.
The match to follow.
Optional. The team the user supports in this match. Used to personalize notifications.
PATCH /user/follow/match/:id/team User
Change the supported team for a match the user is already following.
The followed match ID.
The new team to support.
DELETE /user/follow/match/:id User
Unfollow a match. Stops push notifications and Live Activity updates.
The followed match ID.
Admin match data
GET /admin/sportmonks/fixtures Admin
Fetch fixtures directly from the SportMonks API. Useful for debugging data discrepancies.
POST /admin/cache/clear Admin
Clear cached live match data. Forces the next LiveScoreJob cycle to fetch fresh data from SportMonks.
Clear cache for a specific match. Omit to clear all cached data.