Skip to content

Changelog

This page tracks developer-visible changes to the public Chizumulu API and documentation. Internal implementation changes are omitted unless they affect API behavior. Every entry says whether you need to do anything.

  • Fixed a bug that made one real fixture (Vision S Academy vs Chintheche United) show up as two separate matches, one of them stuck at a stale score. The multiverse remains unproven, so we decided this was probably the more sensible outcome. One observation spelled the away team with a casing typo the registry didn’t recognize, so it split off into a match of its own. Once the registry was corrected, the next update reprojected both records and merged them into one match. No action is needed on your side, and the response shape didn’t change. See Team identifiers.
  • GET /v1/matches: search derived matches by status, competitionCode, teamId, teamAlias or updatedSince, and page through them with a cursor. You no longer need to dig through /v1/structured and assemble the match puzzle yourself. Unlike /v1/live, it returns every match the projection knows about, stale and historical ones included. Nothing to migrate; it is a new route. See GET /v1/matches.
  • GET /v1/teams and GET /v1/teams/{teamId}: the canonical team registry (id, display name, aliases) as JSON, so you can finally stop hardcoding team aliases yourself. It covers the teams canonicalized so far, not every NRFA club. Nothing to migrate. See GET /v1/teams.
  • A normalized numeric minute ("90+4'" becomes 94, or null when it can’t be parsed) now sits next to the literal minuteText, on /v1/structured match and event objects and on the derived-match endpoints (/v1/live, /v1/matches, /v1/matches/{matchId}). Time was already passing; now the API can tell you that as a number too. The addition itself needs no action; see the rename under Changed.
  • On the derived-match endpoints only, the field that held the literal minute text was renamed from minute to minuteText, and the new numeric minute takes its place. This touched only /v1/live and /v1/matches/{matchId}, which had shipped a few days earlier; the minuteText on /v1/structured was never affected. We found no integration using the old field, so no client action is required. If you had already started parsing the old text field on those two routes, point it at the new name.
  • Fixing a team name no longer means manually cleaning up old derived matches: when the team registry changes, affected matches are now reprojected automatically instead of waiting for an unrelated new observation. This closed several known cases where a fixture appeared twice because of an unrecognized team-name spelling or casing (Chipolopolo, Ekwendeni Fc, Lube Masters Fc, Vision Academy). No client changes required.
  • When the docs stop being enough, there is now somewhere to go: a bilingual Get Help page with self-service answers by category and a path to developer support.
  • GET /v1/live and GET /v1/matches/{matchId}: a derived-match projection over structured observations, so you no longer have to work out “what is live right now” from raw posts yourself. The live view is deliberately conservative: a match that goes quiet drops out until its next update, but it stays stored and readable by its id. The second route gives you one match’s full update history. New routes, nothing to migrate. See Derived matches.
  • attachmentFacts on /v1/structured items and history observations: facts read from an image (currently league standings tables) no longer vanish when a post has no structured result; they show up here instead. Responses that already had a structured result are unchanged, so no action is needed.
  • Initial public documentation, OpenAPI schema and llms.txt: the API finally came with a map. Publicly documented endpoints at launch: GET /v1/structured (and /{rawUpdateId}/history), GET /v1/updates, GET /v1/latest, GET /v1/feed, GET /v1/status. Nothing to do; this is the starting line.
  • GET /v1/structured filters: competition, team, postType, teamId (canonical team identifiers) and teamAlias (case-insensitive shorthand), so you can ask for one club without matching spellings by hand. See Team identifiers and Team aliases.
  • GET /v1/videos and GET /v1/videos/latest: a small cached pass-through of one public YouTube channel feed, for when your app wants the videos too.
  • Retained images may be read for one kind of structured data: league standings tables, surfaced as a standings fact. We read the table so you don’t have to squint at it.
  • CORS is now enabled on public GET routes (Access-Control-Allow-Origin: *), so browser-based clients can call the API directly. No action required.
  • The API and processor are served only from their custom domain; no platform-default preview URL is available. If you were calling any other hostname, switch to the documented base URL.