Make your first request in seconds.

No key required to start testing

Request any public-preview endpoint. Every payload arrives in a predictable envelope with execution metadata and stable IDs.

curl "https://openfootapi.com/v1/matches?date=2026-08-28" \
  -H "Accept: application/json"

Response

{
  "data": [
    {
      "id": "match_olg_83156",
      "competitionId": "comp_bundesliga_de",
      "status": "scheduled",
      "kickoffAt": "2026-08-28T18:30:00.000Z",
      "homeTeam": { "id": "team_olg_40", "name": "FC Bayern München" },
      "awayTeam": { "name": "VfB Stuttgart" }
    }
  ],
  "meta": {
    "count": 1,
    "environment": "beta",
    "access": { "authenticated": false, "plan": "public" }
  }
}

Bearer API keys

A Developer API key unlocks paginated results, live events, lineups, xG shot maps and 25,000 measured requests per month. Raw keys start with fs_live_; OpenFootAPI stores only a SHA-256 hash.

What is actually available

Every relevant response includes source and license metadata.

Endpoints

Filter matches without learning provider IDs

Filters can be combined. Dates are interpreted as UTC calendar dates and entity filters use stable OpenFootAPI IDs returned by search.

Use the same endpoint from any stack

Select any endpoint and programming language below to view production-ready boilerplate with authentication, error handling, and response processing.

// TypeScript / Modern Node.js (Fetch)
const url = "https://openfootapi.com/v1/matches?date=2026-08-28&status=scheduled";
const headers: Record<string, string> = {
  "Accept": "application/json",
  
};

async function fetchFootballData() {
  try {
    const response = await fetch(url, { headers });
    if (!response.ok) {
      const err = await response.json();
      throw new Error(err.error?.message || `HTTP ${response.status}`);
    }
    
    const payload = await response.json();
    console.log("Success:", payload.data);
    return payload.data;
  } catch (error) {
    console.error("API Request Error:", error);
  }
}

fetchFootballData();

One envelope across every endpoint

Successful requests return data and meta. Failed requests return error and a request ID that can be used for support and log tracing.

Match context & Intelligence

The context and analytics endpoints compute an integration-ready snapshot from available match history, tactical models and live streams.

Typed, predictable errors

Errors use stable codes, including invalid_api_key, monthly_quota_exceeded, api_key_required and source_unavailable.