LIGR Developer Platform
Build on the LIGR live sports graphics platform.
Create matches, feed scores, fire graphics, react to events, and ship code or native Rive graphics.
REST APIMatches, facts, teams, overlays, streams and themes. JSON in and out. Scoped keys with expiry.ReferenceWebhooksSigned POST requests for match, fact, summary, team, competition and overlay changes, per competition. Off by default. Ask your LIGR contact to turn them on.EventsGraphics SDK BetaWrite a graphic in HTML and JavaScript. Talk
ligr.gfx.v1 to the overlay. Push it into a theme you own, then publish it.Start buildingRive graphics BetaImport native Rive runtime or source projects. Bind live sports data, publish exact versions, and create operator presets.Import RiveGuidesScore a match, configure and automate a stream, receive webhooks, and publish a theme version. Step by step.All guidesYour first request
Section titled “Your first request”Create an API key in the dashboard under Organization settings → Developers → API keys. Give it
matches:read. Send it in the Authorization header as a Bearer token.
curl 'https://api.ligr.live/rest/v2/matches?limit=1' \ -H 'Authorization: Bearer YOUR_READ_KEY'{ "matches": [ { "id": 1188213, "name": "Sydney FC v Melbourne City", "sport": "football", "date": "2026-09-12T09:30:00.000Z", "competitionId": 2311, "competitorsType": "teams", "liveStatus": "pregame", "finishedStatus": "default" } ], "total": 412, "returned": 1}Where to go next
Section titled “Where to go next”AuthenticationAPI keys, per-resource scopes, expiry, and how LIGR isolates organizations.
ConceptsThe competition tree, the theme tree, and the ids that join them.
Verify webhook signaturesHMAC-SHA256 over v0:timestamp:body.
For AI agentsllms.txt, Markdown twins of every content page, and the rules an agent must follow.
Latest in the changelog
Section titled “Latest in the changelog”2026-10-27 — A Rive write warns when an enum binding reads a theme variable that the enum does not list