Build on Sporfie
A REST API and an MCP server for the events, video and live streams your organization already runs on Sporfie. Create events from your booking system, push live scores, cut highlights, receive webhooks — or just ask your AI assistant.
Works in the AI tools you already use
Sporfie ships an MCP server that exposes the Public API as 19 curated tools. Connect it once and ask in plain language. Every tool call is a regular API call underneath — same identifiers, same permissions, same rate limits.
- Claude
- ChatGPT
- Grok Bot
- Cursor
- and any other MCP-compatible client
Streamable HTTP transport. Help Center tools work without a token.
One-click connect
Add the server with no header and your client runs the standard MCP OAuth flow: sign in to Sporfie once, approve the connection, done. No key to copy.
Or bring your own key
For CLIs, CI and scripts, create a personal key in Settings → Developer and pass it as a Bearer header. The same key also works for direct REST calls.
Manage API keysWhat the tools cover
Create, read, update, close and delete events · search and live lookup · places and sports · highlight moments · event webhooks · Help Center search.
Ask instead of integrating
Three conversations that only use tools the Sporfie MCP server actually exposes.
Done — I read 6 matches from the photo and scheduled them on your camera places:
- Sat 09:00 · U14 Tigers – Falcons · Court 1
- Sat 10:30 · U16 Tigers – Ravens · Court 1
- Sat 12:00 · U19 Tigers – Bulls · Court 2
- + 3 more on Sunday
Each one records and streams automatically when it starts. Want me to add a webhook so your website updates as they go live?
Here's what I found for the Spring Cup final (26 Apr, Court 1):
Most watched: the match point at 2:31:07, with 412 views.
Views are counted per highlight clip. The API doesn't report live-stream viewers.
The U19 final is scheduled Saturday 14:00–16:00 on Court 2, so the event is ready. RTMP ingest URLs are issued per encoder inside Sporfie rather than through the API, so the quickest route is:
- Open Settings → Encoders and add your GoPro (or pick it).
- Copy its RTMP URL into the GoPro app.
- Or show the GoPro QR code and scan it with the camera — it configures the stream for you.
Illustrative conversations. Wording varies by assistant; the tool calls are real.
What you can build
Everything below is in the public OpenAPI spec today — no roadmap items.
Events, on your IDs
Create, update, close and delete events. Address them by your own externalID so your system stays the source of truth.
Scheduled recording
Attach an event to a camera-equipped place with a start and end time and it records and streams by itself.
Live scores
Push a score stream from your scoring app or device; the scoreboard and event follow.
Highlights on demand
Register a click at a timestamp and Sporfie cuts a clip around it — from a button, a sensor or your own logic.
Webhooks
Watch an event and receive the full event object on every change. Prefer it over polling.
Moments, reels and bookmarks
Read clip URLs and view counts, manage reels and bookmark collections, export tagged clips.
Embed the player
The Sporfie player drops into any page as an iframe.
Five calls cover most integrations
Straight from the docs. Set SPORFIE_TOKEN, COMPANY_KEY and PLACE_KEY in your environment and these run as-is.
curl -X POST "https://api.sporfie.com/public/events/booking-48213" \
-H "Authorization: Bearer $SPORFIE_TOKEN" \
-H "Content-Type: application/json" \
-d @- <<JSON
{
"companyKey": "$COMPANY_KEY",
"name": "U16 semi-final",
"sport": "volleyball",
"homeTeam": "Tigers",
"awayTeam": "Falcons",
"placeKey": "$PLACE_KEY",
"scheduledStartTime": 1757683200000,
"scheduledEndTime": 1757690400000
}
JSON
# → { "eventKey": "-Nq7xK2mBv9pL3aRt8Zc" }›Verify your key first
curl -o /dev/null -w '%{http_code}\n' \
-H "Authorization: Bearer $SPORFIE_TOKEN" \
https://api.sporfie.com/public/sports
# 200 means the key works. 401 means it doesn't.How access works
Create a personal key
In Settings → Developer. The secret is shown once — store it in a secret manager.
It acts as you
A key reaches the organizations you administer and can be narrowed to specific ones at creation. Every call is checked against your live membership.
Call the API or connect MCP
REST at api.sporfie.com, tools at mcp.sporfie.com — same key, same scope, same limits.
Need to manage organizations you don't administer? That takes a Sporfie-issued integration key.
Talk to usGood to know
- About 1 request per second per key. Pace bulk work and back off on 429.
- All times are UTC milliseconds since the Unix epoch.
- Event watches expire after 12 hours — re-register on a schedule.
- A click is accepted, not finished: clips take a few seconds. Poll the moment if you need the file.
- Keys belong server-side. Never in a browser, mobile app or repository.
Start building
The full reference, the OpenAPI spec and a guide written for AI agents are at docs.sporfie.com.
Guide for AI agents