Your servers
GET /servers
The servers this key reaches: id, name, platform and map. Start here to find a server's id.

Put your DayZ server's leaderboard, killfeed and stats on your own website, or let an AI app read them. Make a key on your server's dashboard, call the API with it, and show the "Data from killfeed.com" credit that comes with every answer.
curl -H "Authorization: Bearer YOUR_KEY" "https://killfeed.com/api/v1/servers/{serverId}/leaderboard"
Send the key as Authorization: Bearer skn_d_…, or as an X-Api-Key header. Every API address starts https://killfeed.com/api/v1.
https://*.example.com covers its subdomains.GET /servers lists the ones a key reaches.Every answer is JSON with your data and the credit, like this:
{
"data": { … },
"attribution": {
"text": "Data from killfeed.com",
"url": "https://killfeed.com/leaderboard/server/12345678",
"note": "Show this credit with a link wherever you show the data."
}
}
Show attribution.text as a link to attribution.url wherever the data appears. Answers also carry an X-Data-Source: killfeed.com header.
An error is { "error": { "code", "message" }, "attribution" } with its HTTP status: 401 a key that isn't valid, 403 a paused key or a server it doesn't reach, 404 nothing there, 429 too many calls (wait for Retry-After seconds), 503 try again shortly.
No answer ever carries a Discord id or a raw log line. Kill positions are in the killfeed only when the server's owner switched them on.
Limits are per key. Answers are kept for about 30 seconds, so asking more often only returns the same data: refresh a page every minute or so. The RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers say where a key stands.
| Plan | Calls a minute | Calls a day | Keys |
|---|---|---|---|
| Free | 60 | No limit for now | Up to 25 for now |
| Paid | 300 | No limit for now | Up to 25 for now |
Everybody is on the Free plan to start.
GET /servers
The servers this key reaches: id, name, platform and map. Start here to find a server's id.
GET /servers/{serverId}
One server: whether it is up and how many are online, its killfeed totals (today, this week, this month, all time) and its place on the global server board.
GET /servers/{serverId}/leaderboard
The server's own player board, 25 a page.
| Parameter | Values | Default |
|---|---|---|
sort |
kills, score, kd, longest, playtime, headshots, streak | kills |
limit |
1-100 | 25 |
page |
1-1000 | 1 |
GET /servers/{serverId}/players/{playerId}
A player's stats on this server and their place by kills. playerId comes from a leaderboard row.
GET /servers/{serverId}/killfeed
The newest events of the last 7 days, newest first. Positions are included only when the server's owner turned them on.
| Parameter | Values | Default |
|---|---|---|
type |
all, kill, pve, connection | all |
limit |
1-100 | 25 |
before |
an event id. For the next page, pass the answer's next. | – |
GET /servers/{serverId}/weapons
The weapons with the most player kills on this server, and the longest kill with each.
| Parameter | Values | Default |
|---|---|---|
days |
1, 7, 30 | 7 |
GET /servers/{serverId}/factions
The server's factions by kills: name, tag, description and member count (never who is in them).
| Parameter | Values | Default |
|---|---|---|
page |
1-100 | 1 |
GET /leaderboard
Skynet's global boards across every Xbox and PlayStation server.
| Parameter | Values | Default |
|---|---|---|
board |
players, factions, servers | players |
sort |
score, kills, kd, longest, headshots | score (players), kills (factions, servers) |
q |
a name to search for | – |
limit |
1-50 | 25 |
page |
1-1000 | 1 |
GET /usage
Your plan, your limits and how many calls this key has made today.
Each reads a server's leaderboard. Put your server's number in place of {serverId} and your key in place of YOUR_KEY.
const answer = await fetch("https://killfeed.com/api/v1/servers/{serverId}/leaderboard", {
headers: { Authorization: "Bearer YOUR_KEY" },
}).then((r) => r.json());
console.log(answer.data);
// In a web page, use a key locked to your website. Show answer.attribution.text with a link to answer.attribution.url on your page.
<?php
$ch = curl_init("https://killfeed.com/api/v1/servers/{serverId}/leaderboard");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["Authorization: Bearer YOUR_KEY"]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$answer = json_decode(curl_exec($ch), true);
curl_close($ch);
// Show $answer['attribution']['text'] with a link to $answer['attribution']['url'] on your page.
import requests
answer = requests.get("https://killfeed.com/api/v1/servers/{serverId}/leaderboard", headers={"Authorization": "Bearer YOUR_KEY"}, timeout=10).json()
print(answer["data"])
# Show answer["attribution"]["text"] with a link to answer["attribution"]["url"] on your page.
The same data, for an AI app that speaks MCP (Claude, Cursor and others), with the same key. Ask it to build your website's leaderboard page and it can read the endpoints and write the code.
Address: https://killfeed.com/mcp/data. Send the key as Authorization: Bearer YOUR_KEY. For Claude Code:
claude mcp add --transport http skynet-data https://killfeed.com/mcp/data --header "Authorization: Bearer YOUR_KEY"
To manage your server with an AI app instead, use the dashboard's AI Connections tab.
Questions? Open a ticket, or read the FAQ.