Introduction

1. 1Create a keySign up free (500 requests a month, no card) and copy your key from the dashboard. Or try every endpoint first in the playground.
2. 2Call the REST APISend x-api-key with every request to https://api.citoapi.com/api/v1. Call it from your server, bot or script, never from a browser.
3. 3Read the envelopeEvery response has the same shape: success, the data you asked for, and meta with pagination and request details. Errors carry a machine-readable code.
4. 4Go liveWhen polling isn't enough, switch to live streams or webhooks so updates come to you.

Example response from GET /cs2/matches/upcoming?limit=1

{
  "success": true,
  "data": [
    {
      "id": "cs2-match-2399865",
      "status": "upcoming",
      "startsAt": "2026-10-21T22:00:00.000Z",
      "bestOf": 3,
      "eventName": "CCT 2026 South America Series 7"
    }
  ],
  "meta": { "...": "pagination and request details" }
}

IDs and slugs

Every match, team, player, fighter and event has a stable id (cs2-match-2399610, ufc-13063) and most have a readable slug. Get them from a list or search endpoint; never build them by hand.

Plans and limits

Each plan has a per-minute and a monthly request limit. Going over returns 429 with RATE_LIMIT_EXCEEDED (slow down) or MONTHLY_LIMIT_REACHED (allowance used).

Live delay

On Free and entry plans, live endpoints return data about 60 seconds behind; Pro and above get it in real time. The X-Cito-Data-Delay-Seconds and X-Cito-Data-Age-Seconds response headers tell you which you got.

Freshness

Live and odds rows carry when we captured them (capturedAt or observedAt), so you can show or check how current a value is.

More detail: authentication, rate limits & plans and errors.