The world's easiest
La Liga API for developers ballers.

Fixtures, scores, standings, clubs, players, match statistics, goal events, xG, head-to-head history, and odds are available through connected routes. Each response keeps canonical match and club identifiers so a product can move from a schedule into detail. The reference section on this page shows the plan floor for each capability.

Freshness depends on the dataset rather than one page-wide timer. Live scores and player statistics can refresh during matches, while fixtures, rosters, injuries, and historical rows use slower cadences. Read the source date and response metadata before deciding how often your application should poll.

Create an account and API key, then send it as a Bearer token. Start with the La Liga matches or standings route so a healthy response is useful even when no match is live. Keep the returned canonical IDs for the detail calls that follow.

Discover identifiers from list responses instead of guessing them from names. Match and standings rows provide the club or match identity needed by detail routes. Preserve those IDs in your own records because accents, abbreviations, and transfers make name joins unsafe.

The exact season range depends on the dataset and your plan. Use the coverage response and the season labels returned by each route before promising a date range to users. Founder plans expose current-season evaluation on Free, up to five seasons on Solo and Trio, and available history on Edge and Pro.

La Liga seasons span two calendar years, so retain the served season label rather than deriving it from kickoff year alone. Read match status to distinguish scheduled, live, finished, postponed, suspended, or cancelled fixtures. A current table and a future fixture window can legitimately carry different dates.

Player-season statistics include goals, assists, minutes, and expected metrics where the source provides them. The xG leaderboard is published only when its completeness checks pass. Treat a missing value as unavailable, not as a measured zero.

xG needs the Solo plan or above. The expected_goals field of /v1/matches/:id/statistics and the player-season leaderboard at /v1/leagues/:id/xg-leaders both start at Solo. The rest of the team stats on /v1/matches/:id/statistics — possession, shots, passes and the rest of the box score — stay available on Free. Coverage is the big five European leagues.

Soccer match events cover goals, cards, substitutions and event timing. Scoring events are included on the Free tier through the default goals view. The full minute-by-minute stream is a Pro feature, with every event stamped to the minute it happened on. Use the canonical match ID from the schedule or match list to request them.

An empty list can be a healthy response for a valid filter with no matching rows. A null field means the value was unavailable or redacted, and it should not be converted into zero. Check status, pagination, metadata, and the requested season before diagnosing a data gap.

The soccer availability surface records absences rather than an NFL-style weekly injury designation. An absence can reflect injury, suspension, or another stated reason, so preserve the reason supplied by the record. Read its source date separately from the live-score timestamp.

Your plan and response headers define the enforceable request limits. Poll live matches more frequently than schedules, rosters, or completed historical statistics. Back off on a 429 response instead of retrying at the same cadence.

Source corrections can change a completed match or player row after the final whistle. Keep canonical IDs so an updated value replaces the same record rather than creating a duplicate. Use the latest source date exposed by the response when auditability matters.

Commercial use depends on your plan and the applicable terms for the fields you use. API access does not itself grant redistribution, sublicensing, trademark, or media rights. Review the terms before shipping a public or customer-facing integration.

Match kickoff records use UTC timestamps. Convert them for display at the edge of your application while retaining the original value for sorting and comparisons. Do not infer a season solely from the calendar year because the competition crosses years.

Read the returned match status rather than inferring state from a blank score or an old kickoff time. Preserve status values your application does not yet recognize so future vocabulary changes do not become false finals. Wait for a terminal status before triggering irreversible settlement or notification logic.