eventsfeed
Live soccer data over REST and WebSocket. Everything about a match is in one consistent model:
| Channel | What | Update rate |
|---|---|---|
core |
teams, competition, phase, clock, score | every change |
odds |
1X2, double chance, BTTS, total goals 2.5, odd/even, 1st half 1X2, correct score | sub-second |
stats |
corners, cards, shots, attacks, possession | seconds |
timeline |
goals, cards, corners, with minute and side | every incident |
pitch |
ball position and current action (attack, dangerous attack, corner…) | ~2 s |
players |
per-player stats (goals, assists, shots, passes, tackles, xG, cards) | after full time |
There is also a ready-made pitch widget you can drop on your site with an <iframe>. See Embed.
How it fits together
- REST (
https://api.eventsfeed.dev/v1) returns snapshots. Each response carriesmeta.rev, the revision of what you got. - WebSocket (
wss://api.eventsfeed.dev/v1/stream) sends one snapshot per topic and then only what changed, as JSON Merge Patches. Revisions are contiguous, so you always know whether you missed something. - IDs are stable and opaque:
ev_…(event),tm_…(team),cp_…(competition),pl_…(player).
Limits
Every API key gets 50,000 requests per hour and 3 simultaneous WebSockets. A WebSocket counts one request when it connects and one per sub message; the data pushed to you is free. See Limits.
Next: Quickstart.