DEVELOPER · TELEMETRY · LAST 7 DAYS
API USAGE
Traffic on the public BrettZone API.
Clients are counted by anonymous hash (no raw IPs stored); callers sending an
X-API-Key header appear by name below.
Raw data: GET /brettZone/api.php/usage?days=7
REQUESTS
72
UNIQUE CLIENTS
4
AVG RESPONSE
39.9 MS
DATA SERVED
1.1 MB
ERROR RATE
5.56 %
REQUESTS PER DAY
JUL 4
PEAK 63/DAY
JUL 10
TOP ENDPOINTS
| Endpoint | Requests | Errors | Avg ms | |
|---|---|---|---|---|
| / | 8 | 0 | 0 | |
| /cages | 8 | 0 | 3.3 | |
| /bots | 6 | 3 | 221.5 | |
| /tournaments | 5 | 0 | 0.8 | |
| /fights/recent | 5 | 0 | 42.6 | |
| /search | 3 | 0 | 119.3 | |
| /usage | 3 | 0 | 0 | |
| /fights/last24h | 2 | 0 | 7.5 | |
| /clips | 2 | 0 | 1 | |
| /cages/{cageNum} | 2 | 0 | 3.5 | |
| /schedule | 2 | 0 | 3 | |
| /bots/{botName} | 2 | 0 | 81 | |
| /bots/{botName}/fights | 2 | 0 | 13.5 | |
| /video-feeds/fight/{tournamentID}/{gameID} | 2 | 0 | 1 | |
| /live/streams | 2 | 0 | 14 | |
| /openapi | 2 | 0 | 0.5 | |
| /tournaments/{tournamentID} | 2 | 0 | 0 | |
| /tournaments/{tournamentID}/players | 2 | 0 | 19 | |
| /? | 1 | 1 | 0 | |
| /tournaments/{tournamentID}/fights | 1 | 0 | 26 | |
| /tournaments/{tournamentID}/fights/{gameID} | 1 | 0 | 1 | |
| /tournaments/{tournamentID}/brackets | 1 | 0 | 276 | |
| /fights | 1 | 0 | 41 | |
| /video-feeds/{recordingID} | 1 | 0 | 0 | |
| /clips/{publicToken} | 1 | 0 | 0 |
STATUS CODES
200
68 · 94.4%
404
1 · 1.4%
500
3 · 4.2%
TOP CONSUMERS
SELF-IDENTIFIED · X-API-KEY
3
ANONYMOUS · CLIENT HASH
1c56691030a7…
63
bdce7775e9fd…
7
7357d8ffd879…
1
e105c5cf17be…
1
HOW THIS IS COLLECTED
Every request to /brettZone/api.php logs its route
template, HTTP status, response time, and payload size to the
apiRequests table after the response is sent.
No raw IP addresses are stored — clients are identified by a one-way hash of IP + user agent.
The same numbers are available programmatically at
GET /brettZone/api.php/usage.