Additive changes stay in v1. Breaking changes require a new major path.
PUBLIC API
Build against the same indexed combat evidence, official war state, Factional Warfare snapshot, and static-universe topology that powers the MISKILLZ and MISMAPS war room.
- BASE PATH
- /api/v1
- AUTHENTICATION
- NONE · PUBLIC GET
- RELEASE
- v1.1.0
- CONTRACT
- v1 STABLE · JSON · CORS *
Archive, pagination, truncation, and upstream freshness travel with the result.
Every v1 response permits cross-origin GET, HEAD, and OPTIONS requests.
No write methods, API keys, private ESI scopes, or hidden account data.
ONE REQUEST, COMPLETE CONTEXT
Responses use a stable envelope with api, resource,generatedAt, data, and—when applicable—meta and links.
curl --get 'https://miskillz.mimgc.net/api/v1/killmails' \
--data-urlencode 'security=LOW' \
--data-urlencode 'minimumValue=100000000' \
--data-urlencode 'pageSize=10'ENDPOINTS
All timestamps are ISO 8601 UTC. Monetary values are ISK.
/api/v1/killmailsSearch and paginate indexed public PvP killmails.
OPEN EXAMPLE ↗/api/v1/killmails/{killmailId}Read one killmail already stored in the public archive.
OPEN EXAMPLE ↗/api/v1/entitiesFind archive-backed pilots, corporations, and alliances.
OPEN EXAMPLE ↗/api/v1/entities/{type}/{entityId}Read an archive-backed entity dossier and activity patterns.
OPEN EXAMPLE ↗/api/v1/warsPage through the persistent official ESI war index.
OPEN EXAMPLE ↗/api/v1/wars/{warId}Read official war identity, totals, and archive coverage.
OPEN EXAMPLE ↗/api/v1/engagements?warId={warId}Read derived per-system engagement groups for a war.
OPEN EXAMPLE ↗/api/v1/frontlinesRead official Factional Warfare state with archive context.
OPEN EXAMPLE ↗/api/v1/map/systemsSearch static-universe systems and stargate adjacency.
OPEN EXAMPLE ↗READ THE META
MISKILLZ separates authoritative upstream state from archived evidence and derived analysis. Coverage objects report counts, time bounds, match percentages, hydration progress, and truncation. “ALL” means all indexed time—not complete EVE history.
BOUNDED RESULTS
Collection endpoints return requested and resolved pages, total results, total pages, and navigation links. Killmails and mapped systems allow up to 200 rows per page; wars allow up to 50.
HONOR CACHE-CONTROL
Cache-Control is authoritative and varies by source freshness. Clients should cache, back off on 503 responses, and avoid bulk polling. Public access is best-effort and has no uptime or throughput SLA.
MACHINE-READABLE
{
"api": { "name": "MISKILLZ Public API", "version": "1.0" },
"error": { "code": "INVALID_WAR_ID", "message": "..." }
}API access does not transfer ownership of EVE Online, official ESI, static data, or zKillboard-sourced records. Keep source attribution, honor published cache policies, and review the Legal, Data & Privacynotice before redistributing results.