# IFC public API > Read-only data of one IFC team (the team of the API key): squad, matches, results, standings and stats. Use it to build the team's own website. Base URL: https://api.the-ifc.fr/public/v1 Full contract (OpenAPI 3.1): https://api.the-ifc.fr/public/v1/openapi.json ## Authentication Send the key in a header: `Authorization: Bearer `. The key names the team: no route takes a team id. The key (`ifc_sk_…`) is a secret. Use it only in server code (a server component, an API route, a backend or edge function), read from an environment variable or the host's secret store. Never write it in client code, a public repository or a prompt, and never ask its owner to paste it in a chat. There is no key for browser code. A site with no server at all stays on its snapshot (see below): add a server function that calls the API, and let the browser call that function. ## Routes - GET /team: The team. - GET /players: The current squad. - GET /players/stats: Each player's validated match stats, best scorer first. Query: since, until, kind. - GET /players/impact: What each player changes to the team's results when he starts. - GET /players/{player_id}: One player, current or former: stats and analysis. - GET /matches: The team's matches. Query: period, limit, offset. - GET /stats: The team's record. Query: since, until. - GET /standings: The ladder of the team's league, from the top. Query: limit. - GET /rivals: The clubs the team has played most, and its record against each. Query: limit. ## Rules for the code you write - GET only. The API changes nothing. - 60/minute per key, and every answer is cached 60 seconds on IFC's side: cache on your side too (for example `revalidate: 60`), never poll faster. - Dates are ISO 8601 in UTC: format them in the visitor's time zone. - A `picture` is an image URL and may be null: plan a placeholder. - A player is a pseudo (`name`), never a real name. `has_account: false` is a player the staff added by hand. - `/matches?period=upcoming` is the fixture list, `/matches?period=past` the results (`result` is W, D or L from the team's side; `goals_for` is the team's score). - Page `/matches` with `limit` (50 at most) and `offset`; `count` is the total. - `/players/impact` and the `analytics` of `/players/{player_id}` are experimental: read their fields defensively. ## Starting from a snapshot A site can be built before it has a key, on a snapshot: a JSON object whose keys are this API's requests ("/team", "/matches?period=past"…) and whose values are their answers, frozen at one date. - Keep every read in one module (for example `src/lib/ifc.ts`) with one function per route. Pages never read the snapshot or call the API themselves. - Without a key, that module answers from the snapshot. With a key, it calls the API and falls back to the snapshot when the call fails (402, 403, network): the site never breaks. - Going live is then one change in that module, nothing in the pages. ## Errors Every error is `{"error": {"code": "...", "message": "..."}}`. - 401 `missing_api_key` / `invalid_api_key`: check the header and the key. - 402 `subscription_inactive`: the key's subscription stopped. Show the site without live data rather than an error page. - 403 `key_suspended`: the key's holder left the team. - 429 `rate_limited`: slow down and cache.