Skip to main content

Your website

Give your team its own website: one prompt builds it with your squad, your results and your stats, and an API key puts it in real time.

What to remember​

You'll find it in your team's My website section. The captain and the co-captains can use it, in two steps.

  1. Create your site (free). A brief is already written in the box: your pages, the mood. Change it as you like, then press Enter: Lovable opens with the whole prompt, your team's data included, and you send it there. You can also copy the prompt for Claude Code or Codex. The example under the box shows what a site can look like with your own data.
  2. Connect it to IFC (subscription). Without a key, your site keeps the data of the day you created it. With one, it switches to real time: players, league and tournament matches, scores, standings and stats. Subscribe, create your key in one click, then paste the connection prompt into your site's project. Show the prompt displays it word for word before you copy it. Once your key exists, this is also where you replace it, revoke it and manage your subscription.

Good to know​

  • Your team's data is frozen once. The first time you create a site, IFC takes your squad, results, standings and stats as of that day. Every site of your team starts from that same data; the key is what keeps it moving.
  • The key reads your team's data only, and changes nothing. Players appear by their pseudo, never by their name.
  • One secret key. It goes on your site's server (Lovable's secret form, or an environment variable for Claude Code and Codex): it's the one the connection prompt asks for. It is shown only once: lost or exposed, generate a new one, the old one stops at once. A site with no server at all can't hold a secret: it stays on the data of the day you created it.
  • Never paste your secret key in a chat or in your code. The connection prompt doesn't contain it: it tells your tool how to ask you for it safely.
  • The key is yours. It works as long as your subscription runs and you're a member of the team, even as a plain player. If you leave the team, it stops. Your subscription is managed separately: cancel it from Connect it to IFC.
  • If your subscription stops, your site goes back to the data of the day you created it, without breaking. It updates again as soon as you resubscribe.
  • One key per account, for one team.

For developers​

The API is read-only and answers for the team of the key: no route takes a team id. Its reference and a guide for AI assistants are public:

Send the key as Authorization: Bearer <key>. Limits: 60 requests a minute per key, and answers are cached 60 seconds.