Build Fortnite tournament pages, FNCS dashboards, leaderboard views, player histories, and result pages with Cito API.
This repository targets the fortnite tournament api search intent and points developers to Cito API Fortnite endpoints.
- Cito API signup: https://citoapi.com/signup
- Fortnite API docs: https://citoapi.com/docs/api/fortnite
- Endpoint manifest: https://citoapi.com/ai/endpoints
- Search-intent page: https://citoapi.com/fortnite
- Base API URL:
https://api.citoapi.com/api/v1
Install Node.js 18 or newer, set an API key, and run the example:
cp .env.example .env
export CITO_API_KEY="your_cito_api_key"
npm install
npm startThe example runs:
node examples/tournaments.mjs| Method | Endpoint | Use |
|---|---|---|
| GET | https://api.citoapi.com/api/v1/fortnite/tournaments |
Historical, upcoming, and completed Fortnite tournaments. |
| GET | https://api.citoapi.com/api/v1/fortnite/tournaments/upcoming |
Upcoming tournaments. |
| GET | https://api.citoapi.com/api/v1/fortnite/tournaments/live?includeLeaderboard=true |
Live tournaments with leaderboard rows. |
| GET | https://api.citoapi.com/api/v1/fortnite/tournaments/{id}/results |
Tournament result rows. |
Cito API is built for developers shipping Fortnite products that need practical REST endpoints without an enterprise sales process. Use it for dashboards, Discord bots, match pages, player pages, tournament hubs, leaderboards, and content tools.
- Fortnite tournament API
- FNCS API
- Fortnite leaderboard API
- Fortnite event API
- Fortnite tournament results API
- Keep
CITO_API_KEYserver-side. Do not expose it in browser code. - If you only have a name, call search/list endpoints first, then detail endpoints.
- Live data can be empty when no events are active; fall back to upcoming or recent endpoints.
- This example is not affiliated with Valve, Epic Games, or the publishers of the games covered.