EF-Map API Access

This page is for trusted third-party builders working on EVE Frontier tools, dashboards, overlays, bots, and research projects. If you reached it because a request to an ef-map.com/api/* endpoint returned a no_origin message, you are in the right place — it explains what API access is, why some endpoints are protected, and how to request a partner key.

What this page is

EF-Map serves most of its experience directly in your browser, but it also exposes a set of heavier shared-data endpoints under https://ef-map.com/api/*. To keep those endpoints fast and affordable for everyone, they are protected.

• Normal EF-Map use is automatic. When you use the map at ef-map.com, the site's own requests are recognized as same-origin browser traffic and just work — no key, no setup.
• Third-party tools and scripts may need a key. A standalone tool, bot, spreadsheet, or backend service that calls these endpoints from outside the site does not look like a browser on ef-map.com, so it needs an EF-Map API key.

Why API access is controlled

The protection is not about locking the community out. It exists so EF-Map stays healthy:

• Prevent abuse and scraping that would otherwise hammer the shared endpoints.
• Keep hosting costs predictable. These endpoints are backed by Cloudflare Workers and KV/edge storage, and uncontrolled traffic translates directly into cost.
• Keep EF-Map reliable for players who are using the live map.
• Let trusted builders integrate responsibly through a stable, supported surface instead of fragile scraping.

What access can cover

Access is granted per scope. A scope is a named group of related read-only endpoints, so a key only carries the data categories a project actually needs. Each scope below links to a live example request and response so you can see the data shape before requesting access. The current scope groups are:

Requesting access

Access is granted case by case. When you reach out, it helps to include:

• Who you are / project name — you and the tool you are building.
• What you are building — a short description of the tool and its audience.
• Which endpoints / data you need — the scopes above that fit (it is fine to ask for guidance).
• Expected traffic — rough request volume and how often you will call.
• Public or private — whether the tool is public, private, or internal to a tribe/group.
• Contact method — how to reach you for key delivery and any follow-up.
• Attribution — whether you can credit and link EF-Map if the tool is public.

Contact

Email [email protected] with the details above to request a key. For abuse reports or a compromised key, use [email protected].

There is no automated self-service signup. Keys are issued manually to keep the partner surface trustworthy, so allow a little time for a reply.

Using a key

Once you have a key, send it on every request in the X-API-Key header. Same-origin browser traffic from ef-map.com does not need this; external callers do.

# curl
curl -H "X-API-Key: YOUR_API_KEY" https://ef-map.com/api/killboard-snapshot

// JavaScript fetch
fetch('https://ef-map.com/api/killboard-snapshot', {
  headers: { 'X-API-Key': 'YOUR_API_KEY' }
})

Replace YOUR_API_KEY with the key you were issued. Your key only unlocks the scopes granted to it; a request for an endpoint outside those scopes returns an insufficient_scope error.

Responsible use

• Cache responses where you can. This data does not change second-to-second, so cache it and reuse it.
• Avoid aggressive polling. Poll on sensible intervals rather than in a tight loop. A generous per-IP rate limit protects the service as a safety net, and well-behaved tools never get close to it.
• Do not redistribute or embed your key in public client-side code, shared repos, or other people's tools. Treat it like a password.
• Ask before building a high-volume integration. If you expect heavy or unusual traffic, mention it up front so we can plan for it.
• Keys can be rotated or revoked. If a key is leaked, abused, or simply needs refreshing, it can be rotated or revoked at any time. Let us know if yours is exposed and we will issue a new one.

Not everything is available

The partner API is a curated, read-only surface — not a full backdoor to EF-Map internals. Some things are intentionally out of scope:

• Some endpoints are same-origin only and are not offered to third parties at all.
• Some surfaces are wallet-, subscription-, or allowlist-scoped (for example identity-aware or partner-specific app routes) and are not part of the general partner key.
• Admin and operational endpoints are not exposed.
• Raw backend service hostnames are not a supported integration target. Integrate only through https://ef-map.com/api/*; the underlying data services are an internal boundary and may change.
• Access is read-only unless something else is explicitly agreed.

EVE Frontier is a CCP Games / community universe; EF-Map is an independent community tool. Indexed data can be delayed, incomplete, or inference-heavy — treat it as evidence, not absolute live truth. For general questions see the FAQ and About pages.