JavaScript Apex API guide

Apex Legends APIwith JavaScript and Next.js examples.

Fetch ALGS events, scores, players, legend pick rates, and transactions from JavaScript or TypeScript without exposing your API key to the browser.

Start Free View Apex API Docs

Built for: Discord bots · ALGS dashboards · Fantasy tools · Betting research · Broadcast overlays · Data products

Next.js readyTypeScript friendlyServer-side keysREST JSON

ALGS API sample

Split 1 Pro League standings

Event data

Team leaderboard

/apex/algs/events/:id/scores

#1Falcons42 K78 pts

#2Alliance35 K64 pts

#3TSM31 K58 pts

Player stat rows

kills · damage · HMS

ImperialHal15 kills4,821 dmg

Effect13 kills4,360 dmg

Verhulst11 kills3,988 dmg

Legend bans

per map

Pick rates

global stats

Transactions

rosters

ALGS data coverage

What Apex Legends and ALGS Data Can You Access?

Concrete Apex Legends esports data categories developers can use for dashboards, bots, fantasy tools, research products, and match centers.

ALGS events, regions, schedules, and match listings

Series standings with points, kills, placement, and HMS

Player-level rows for kills, assists, damage, knockdowns, and team context where available

Legend pick rates, kills, damage, bans, and team composition data

Roster transactions, team changes, role updates, and player search

Tournament-level team stats, player stats, games, and historical event data

Normalized fields designed for developer dashboards, bots, and analytics pipelines

500

free API calls/month to test

$25

starter paid plan, no contract

ALGS

events, scores, rosters, and meta data

Developer endpoints

JavaScript-ready Apex endpoints

Build ALGS event pages, standings tables, player profiles, legend meta pages, roster trackers, and Discord bots from documented endpoints.

GET/v1/apex/algs/events

List ALGS events with region, schedule, and status filters.

GET/v1/apex/algs/events/{seriesId}/scores

Series standings, HMS, team stats, player rows, legends, and compositions.

GET/v1/apex/algs/global-stats/{eventId}/legends

Legend pick rates, kills, damage, and team composition data.

Next.js route handler example

export async function GET() {
  const response = await fetch("https://api.citoapi.com/api/v1/apex/algs/events", {
    headers: {
      "x-api-key": process.env.CITO_API_KEY!
    },
    next: { revalidate: 60 }
  });

  return Response.json(await response.json());
}

Ship Apex data safely in web apps

Keep API keys in server-side route handlers, workers, or backend services instead of exposing them in browser JavaScript.

Cache ALGS event and stats responses to stay inside plan limits while keeping product pages fast.

Use the same integration pattern for dashboards, bots, static pages, and internal tools.

Use cases

Built for developers shipping Apex and ALGS products

ALGS analytics dashboards

Build event pages, team leaderboards, player tables, legend meta views, and post-series analysis without maintaining your own scraper.

Discord bots and communities

Return standings, match scores, player cards, legend bans, and roster updates through bot commands backed by REST JSON.

Fantasy and pricing models

Use points, kills, HMS, damage, knockdowns, pick rates, and player-level rows as inputs for fantasy scoring or pricing algorithms.

Questions developers ask

Can I use Cito API with Next.js?

Yes. Use Cito from Next.js route handlers, server actions, API routes, or backend workers so your API key stays private.

Can browser code call Cito directly?

Do not expose your Cito API key in browser code. Call Cito from your backend and return only the data your frontend needs.

Can I cache Apex API responses?

Yes. Caching event and stats responses is recommended for dashboards, SEO pages, and bots.

Start building with Apex Legends data today

Get a free Cito API key, test ALGS endpoints, and upgrade only when your product needs more volume.

Create Free API Key