Your ELO meetings with a team today
const url = 'https://foxleague.ai/api/matches/elo-pair/1';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://foxleague.ai/api/matches/elo-pair/1 \ --header 'Authorization: Bearer <token>'The ELO pair cap between your team and team user_id: how many of your meetings with that team moved ELO since the last daily reset and whether a game against it applied now would move none (no_elo). From the cap’s start (elo_pair_cap.live_from in GET /api/config) the same two teams move ELO in at most elo_pair_cap.per_day meetings (3 unless the game settings say otherwise) per day, from the daily reset at reset_hour_utc (UTC) to the next, ranked games, 1v1 challenges and tournaments together; a later meeting that day still counts for the result, points, prizes and XP. Only results already applied count: a match that has not ended yet (a tournament match until the end of its broadcast) is not in meetings. A forfeit is never a meeting. Before the cap’s start live is false and meetings is 0. The cap is judged when a result is applied (a 1v1 at the end of its broadcast), not when you read this: with no_elo true, no_elo_until says until when a result would still move no ELO: the next daily reset. The app shows a line naming that time before a 1v1; nothing is refused.
Who: a signed-in player.
Refusals:
Not registered: the session wallet has no account.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The other team’s user id.
Responses
Section titled “ Responses ”Success or a refusal: read success (the refusals are in the description).
object
A machine-readable reason next to error, set only where the caller must act differently. tx_pending: the payment was not refused but could not be verified yet; keep the transaction hash and confirm again with the same hash, never pay twice.
The answer. Present when success is true.
object
The meetings of the same two teams that move ELO per day (3 unless the game settings say otherwise).
Whether the cap governs now.
Your meetings with this team that moved ELO since the last daily reset, counted from the cap’s start. Only results already applied count; a meeting that moved no ELO because of the cap does not count.
True when a game against this team applied now would move no ELO for either team: the cap governs and meetings has reached cap.
With no_elo true: until when a game’s result would still move no ELO (RFC 3339, UTC), the next daily reset, when the count of every pair starts again at 0. A result from this instant on moves ELO. Null when no_elo is false.
The other team’s name; null when that user has no team.
The hour (UTC, 0 to 23) the day of the cap starts and ends: the daily reset, 14 unless the game settings say otherwise.
Why the request was refused, in plain words. Present when success is false.
true when the request did what it asked. false is a refusal: read error.
Example
{ "data": { "cap": 3, "live": true, "meetings": 3, "no_elo": true, "opponent_team": "Night Owls", "reset_hour_utc": 14, "no_elo_until": "2026-11-21T14:00:00Z" }, "success": true}No valid session. The body is plain text: Missing Authorization header, Invalid Authorization format, Invalid session token or Session expired or invalid. Sign in again.
Example
Session expired or invalidA server read failed. The body is empty.