Regional Endpoints
Cito API is deployed globally. Use regional endpoints for lower latency when querying region-specific data.
Default Endpoint
The default endpoint automatically routes to the nearest region:
https://api.citoapi.com/v1/...This is recommended for most use cases. Only use regional endpoints if you need guaranteed low latency for a specific region.
Available Regions
| Region | Code | Endpoint | Avg Latency |
|---|---|---|---|
| North America East | NA-EAST | na-east.api.citoapi.com | ~20ms |
| North America West | NA-WEST | na-west.api.citoapi.com | ~25ms |
| Europe | EU | eu.api.citoapi.com | ~30ms |
| Asia Pacific | ASIA | asia.api.citoapi.com | ~45ms |
| Oceania | OCE | oce.api.citoapi.com | ~50ms |
| Brazil | BR | br.api.citoapi.com | ~40ms |
| Middle East | ME | me.api.citoapi.com | ~55ms |
Usage Examples
Using Regional Endpoints
// Query EU endpoint for European matches
const response = await fetch('https://eu.api.citoapi.com/v1/valorant/matches/live', {
headers: { 'Authorization': 'Bearer sk_live_...' }
});
// Query NA-EAST for North American Fortnite data
const response = await fetch('https://na-east.api.citoapi.com/v1/fortnite/matches/live', {
headers: { 'Authorization': 'Bearer sk_live_...' }
});Region Parameter
You can also use the region parameter with the default endpoint:
// Filter by region using query parameter
curl "https://api.citoapi.com/v1/fortnite/matches/live?region=EU" \
-H "Authorization: Bearer sk_live_..."Best Practices
Use the default endpoint for global data
When querying player stats or tournament data that spans multiple regions, use the default api.citoapi.com endpoint.
Use regional endpoints for live matches
When building real-time applications that need the lowest latency, use the regional endpoint closest to your servers.
Implement fallback logic
If a regional endpoint is slow or unavailable, fall back to the default endpoint which will automatically route to a healthy region.