Setup
Connect the data sources
CS2Mate pulls live data from Steam Web API and FACEIT Data API. Steam is required; FACEIT is optional but unlocks per-match history, ELO trends, and windowed stats. Setup takes about 5 minutes total.
Integrations
All connectedSteam Web API
STEAM_API_KEYIdentity · CS2 stats · inventory · friends list
FACEIT Data API
FACEIT_API_KEYELO · per-match history · windowed stats · recent form
Neon Postgres
DATABASE_URLFriends · teams · practice groups · AI chat history
Google Gemini (AI Coach)
GEMINI_API_KEYAI Coach Q&A on /coach with live stats context
FACEIT_API_KEY — how to get one
~3 min- 1
Sign in to FACEIT developers
Go to developers.faceit.com and sign in with your FACEIT account. If you don't have one yet, sign up first — it's free. - 2
Create a new app
Hit + New app on the dashboard. Name it anything (e.g. cs2mate), pick the Server-side type, accept the terms. No callback URL needed for the Data API. - 3
Copy the server-side key
Once the app is created, FACEIT shows a Server-side API key. Copy it — it starts witheyJ…(a JWT). - 4
Add it to Vercel
Open your Vercel dashboard, pick the cs2mate project → Settings → Environment Variables. Add a new variable:Then Redeploy — the production deployment needs to pick up the new env. Either trigger a manual redeploy from the dashboard or push any commit.FACEIT_API_KEYProduction · Preview · Developmentpaste the key here - 5
Verify
Refresh this page. The card above flips to green and your /dashboard starts pulling FACEIT data. If you see “FACEIT player not found”, your Steam account isn't linked to a FACEIT account yet — sign in on faceit.com with Steam once and try again.
STEAM_API_KEY — how to get one~2 min · expand
- 1
Open Steam dev page
Go to steamcommunity.com/dev/apikey while signed in to Steam. - 2
Register a key
Type a domain name (your deployed URL, e.g. cs2mate.com — or localhost for dev). Accept the terms. The key appears immediately. - 3
Add to Vercel
Same as above — add STEAM_API_KEY to Environment Variables, then redeploy.
AUTH_SECRET — sign-in cookiesexpand
Used to HMAC-sign the session cookie + user prefs cookie so they can't be tampered with. Any long random string works — generate one with:
openssl rand -base64 48Then add AUTH_SECRETto Vercel env vars, same path as the other two. Don't rotate it without expecting every signed-in user to be logged out.
Edit your profile
Display name, currency, goals, languages — all in /settings.
Open the dashboard
Once the keys are in, your data lands here within seconds.